Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add TheQmaks/areclaw-plugin/plugin install areclawWrote 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/theqmaks/areclaw-plugin/analyze-apk)<a href="https://agentmods.dev/commands/theqmaks/areclaw-plugin/analyze-apk"><img src="https://agentmods.dev/badge/commands/theqmaks/areclaw-plugin/analyze-apk.svg" alt="Measured on agentmods" 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.00016 | $0.01614 |
| Opus 5 | $0.00008 | $0.00807 |
| Sonnet 5 | $0.00003 | $0.00323 |
| Haiku 4.5 | $0.00002 | $0.00161 |
Grade A, and why
analyze-apk scanned grade A with 1 finding 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 5d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
# adb shell chmod 755 /data/local/tmp/<NAME>-server && adb shell /data/local/tmp/<NAME>-server -D & Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analyze-apk
Perform a comprehensive security analysis of an Android application. This covers APK acquisition, reconnaissance, static analysis, dynamic analysis, and report generation. The workflow adapts its strategy based on what protections and frameworks the app uses.
Instructions
1. Parse input and acquire the APK
If the user provided a file path (contains / or \ or ends in .apk), use it directly. If the user provided a package name, acquire the APK:
# Option A: Pull from connected device
adb shell pm path <package-name>
adb pull <device-path> workspace/samples/
# Option B: Download from store (no device needed)
justapk download <package-name> -o workspace/samples/
Set $APK to the path to the APK file and $PKG to the package name for all subsequent steps.
2. Perform reconnaissance to determine analysis strategy
Run protection and framework detection to decide how to approach the app. Do not skip this phase — it determines everything that follows.
# Protection detection
apkid $APK
# Check native libraries
unzip -l $APK | grep '\.so' | head -20
# Detect framework (Flutter, React Native, Unity, etc.)
unzip -l $APK | grep -E 'flutter|react|index\.android\.bundle|il2cpp|global-metadata'
# Quick manifest extraction
apktool d -s -f -o /tmp/apk_quick $APK
Read AndroidManifest.xml from the extracted output. Based on findings, decide the approach:
- Flutter — Focus on network interception; limited static analysis of Dart.
- React Native — Extract and analyze the JS bundle; check for Hermes bytecode.
- Unity/IL2CPP — Run
tools/il2cppdumper/Il2CppDumper.exe libil2cpp.so global-metadata.dat output/then analyze with Ghidra using recovered symbols. - Packed — Use
clsdumperto dump DEX first, then proceed with static analysis. - Native Java/Kotlin — Full static and dynamic analysis.
- Heavy obfuscation — Identify the obfuscator, try
simplifyfirst, then java-deobfuscator or threadtear.
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.
- 5d ago First seen · 153 lines · 16 tokens per session scan A 75254a46196c
analyze-apk is a command published in the GitHub repository TheQmaks/areclaw-plugin (1 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 1,614 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.