Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/anatoly505/ios-reverse-skills/extract-ipa)<a href="https://agentmods.dev/commands/anatoly505/ios-reverse-skills/extract-ipa"><img src="https://agentmods.dev/badge/commands/anatoly505/ios-reverse-skills/extract-ipa/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/anatoly505/ios-reverse-skills/extract-ipa"><img src="https://agentmods.dev/badge/commands/anatoly505/ios-reverse-skills/extract-ipa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00009 | $0.00923 |
| Opus 5 | $0.00005 | $0.00462 |
| Sonnet 5 | $0.00002 | $0.00185 |
| Haiku 4.5 | $0.00001 | $0.00092 |
Grade A, and why
extract-ipa scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to extract-ipa — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/extract-ipa
Extract an iOS application and perform initial structure analysis.
Instructions
You are starting the iOS reverse engineering workflow. Follow these steps:
Step 1: Get the target file
If the user provided a file path as an argument, use that. Otherwise, ask the user for the path to the IPA or .app bundle they want to analyze.
Step 2: Check and install dependencies
Run the dependency check:
bash ${CLAUDE_PLUGIN_ROOT}/skills/ios-reverse-engineering/scripts/check-deps.sh
Parse the output looking for INSTALL_REQUIRED: and INSTALL_OPTIONAL: lines.
If required dependencies are missing, install them one by one:
bash ${CLAUDE_PLUGIN_ROOT}/skills/ios-reverse-engineering/scripts/install-dep.sh ipsw
The install script auto-detects the OS and installs via Homebrew when possible (brew install blacktop/tap/ipsw), or falls back to downloading from GitHub releases. If installation fails, the script prints exact manual instructions (exit code 2). Show those instructions to the user and stop.
For optional dependencies (INSTALL_OPTIONAL:jtool2, INSTALL_OPTIONAL:frida, etc.), ask the user if they want to install them.
After any installations, re-run check-deps.sh to verify. Do not proceed until all required dependencies pass.
Step 3: Extract and analyze
Run the extraction script on the target file:
bash ${CLAUDE_PLUGIN_ROOT}/skills/ios-reverse-engineering/scripts/extract-ipa.sh <file>
For IPA files: the script extracts the ZIP, locates the .app bundle inside Payload/, runs ipsw class-dump on the main binary, and extracts metadata.
For .app bundles: the script works directly on the bundle.
Options:
-o <dir>— Custom output directory--no-classdump— Skip class-dump (faster, metadata-only analysis)--thin <arch>— Extract a specific architecture from fat binaries (e.g.,arm64)
For obfuscated apps (if the user mentions it or you detect mangled names):
bash ${CLAUDE_PLUGIN_ROOT}/skills/ios-reverse-engineering/scripts/extract-ipa.sh --swift-demangle <file>
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 89 lines · 9 tokens per session scan A 830d331eb601
extract-ipa is a command published in the GitHub repository anatoly505/ios-reverse-skills (9 stars, last pushed 4mo ago), licensed Unlicense. It adds 9 tokens to every session and 923 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to extract-ipa, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
feature-build
Build a complete mobile feature from description to running code with E2E tests. Orchestrates 6 phases - planning, implementation, testing, build-fix, quality gate, and verification. Auto-detects platform.
feature-status
Show the current status of a feature build - which phase is active, what has completed, what remains, and any blockers.
preflight
Audit a build against App Review rejection triggers by app type before submitting.
aso-audit
Audit App Store listing for keyword coverage, metadata limits, and conversion levers.
perf-investigate
Drive an iOS performance or memory-leak investigation on using Memory Graph + Time Profiler. Enforce data-before-architecture and stacked PRs.
feat
Kick off tasks creation for a new feature (4-item interview before invoking pm-agent; an epic-sized requirement routes to phased decomposition, a feature already built on one platform routes to cross-platform parity, a change that touches no endpoint routes to client-only).