Skip to content
SkillModel-led497 tokens in use

competition-crypto-mobile

A downstream CTF-sandbox skill for crypto, encoding, steganography and mobile challenges: recover each transform stage in order and hook the narrowest mobile boundary.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-crypto-mobile

Skill label

measured from its files

What installing competition-crypto-mobile costs

106tokens idle
497tokens in use
689tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples0/15
  • Output10/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity96
  • Maintenance72
  • Community72
  • Maturity28
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers