Skip to content
SkillModel-led541 tokens in use

competition-android-hooking

A downstream CTF-sandbox skill for Android APK analysis: static triage, hooks at the narrowest trust boundary, local storage checks and replay of an accepted request.

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

Skill label

measured from its files

What installing competition-android-hooking costs

116tokens idle
541tokens in use
770tokens, 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 where the decisive path runs through an Android app’s live trust boundary. It starts with the manifest, exported components, deeplinks, native libraries and local storage, then picks the narrowest runtime boundary to observe.

The method keeps static evidence and dynamic traces together before any claim is made. The skill states that it runs only after the orchestrator has set sandbox assumptions.

What You Get

  • A three-step workflow: static triage before hooks, hook the narrowest boundary, replay the accepted path
  • A reference checklist of static targets and preferred hook boundaries such as signer, crypto helper, JNI bridge, keystore and WebView bridge
  • Evidence guidance that pairs a static location with dynamic proof and the local state it depends on
  • A hand-off rule to the broader crypto and mobile skill when transform recovery dominates

Common Use Cases

  • Tracing how an Android app in a CTF builds and signs its requests
  • Inspecting shared preferences, local databases and token storage in a lab APK
  • Documenting the smallest hook set that reproduces an accepted server-side branch

What Makes It Unique

It focuses on the live trust boundary of the app and advises hooking the signer, crypto helper or JNI marshaling, with the user interface layer left alone. Its checklist names the common pitfalls: capturing a signed header without the plaintext that produced it, and ignoring local state such as prefs or keystore material.

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 itself involves decompiling and running an APK, using a hooking framework such as Frida, patching or re-signing the package, and sending requests to a server, so the agent’s own tools perform those actions 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