This skill is a specialization of the ctf-sandbox-orchestrator skill for challenges that depend on recovering a transform chain, a hidden media payload, a mobile signing path or a local trust boundary. The agent first decides whether the dominant path is crypto, stego or mobile, then works the stages in order and records the exact parameters.
The skill states that it runs only after the orchestrator has set sandbox assumptions.
What You Get
- A workflow with three tracks: crypto and encoding, stego, and mobile
- A reference checklist for the transform order from container to final parse, stego carriers and mobile hook targets
- A rule to keep exact keys, IVs, nonces, salts, offsets and byte order in one evidence block
- Hand-off rules to the Android hooking, iOS runtime and stego media skills
Common Use Cases
- Working out a multi-stage decode chain in a CTF blob challenge
- Inspecting image or media metadata, chunk layout and trailers for hidden data in a lab
- Tracing a signer or token storage path in an Android or iOS app in a sandbox
What Makes It Unique
It is the general entry for three related topics and then routes to narrower siblings. Its method asks for a reproduced artifact as the result, since naming an algorithm does not count as recovery, and it warns against scattering transform stages across many notes.
Under The Hood
The skill is instruction text only: a SKILL.md, one reference checklist and an agent configuration file. It ships no scripts. The method can involve decoding files, inspecting images, and running or hooking mobile apps, so the agent’s own tools do that work in the sandbox the orchestrator set up. The skill does not fetch pages or call APIs on its own.