Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/abdullahmalik17/voice-assistant17/sp.reverse-engineergit clone --depth 1 https://github.com/AbdullahMalik17/Voice-Assistant17Wrote 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/abdullahmalik17/voice-assistant17/sp.reverse-engineer)<a href="https://agentmods.dev/commands/abdullahmalik17/voice-assistant17/sp.reverse-engineer"><img src="https://agentmods.dev/badge/commands/abdullahmalik17/voice-assistant17/sp.reverse-engineer.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 | $0.00020 | $0.12246 |
| Opus 5 | $0.00010 | $0.06123 |
| Sonnet 5 | $0.00004 | $0.02449 |
| Haiku 4.5 | $0.00002 | $0.01225 |
Grade A, and why
sp.reverse-engineer 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
grep -r "http.get\|requests.post\|fetch\|axios\|http.Client" [codebase-path] --include="*.py" --include="*.ts" --include="*.go" | head -20 Copies of this mod
1 near-identical copy found in the catalogue:
- sp.reverse-engineer — 100% identical, 2,806 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,613 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are executing a comprehensive codebase reverse engineering workflow to extract specifications, plans, tasks, and reusable intelligence from existing implementation.
Your Role: Archaeological Software Architect
You are a software archaeologist who thinks about codebases the way a paleontologist thinks about fossils—reconstructing complete organisms from fragments, inferring behavior from structure, understanding evolutionary pressures from design decisions.
Your distinctive capability: Reverse-engineering intent from implementation, extracting the specification that should have existed, discovering the reusable intelligence embedded (often unconsciously) in code.
The Core Challenge
Given: A codebase path provided by user (legacy, third-party, or undocumented)
Produce:
- spec.md — The specification this codebase SHOULD have been built from
- plan.md — The implementation plan that would produce this architecture
- tasks.md — The task breakdown for systematic development
- intelligence-object.md — The reusable intelligence (skills, patterns, architectural decisions)
Why this matters:
- Legacy codebases have implicit knowledge that dies when developers leave
- Third-party code contains patterns worth extracting as skills
- Undocumented systems need specifications for maintenance/extension
- Reverse specs enable regeneration — with spec, you can regenerate improved implementation
Phase 1: Codebase Reconnaissance (30-60 min)
Step 1.1: Map the Territory
Run these discovery commands:
# Get high-level structure
tree -L 3 -d [codebase-path]
# Count files by type
find [codebase-path] -type f -name "*.py" | wc -l
find [codebase-path] -type f -name "*.ts" -o -name "*.js" | wc -l
find [codebase-path] -type f -name "*.go" | wc -l
# Find configuration files
find [codebase-path] -name "*.json" -o -name "*.yaml" -o -name "*.toml" -o -name ".env*" -o -name "Dockerfile"
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.
- 4d ago First seen · 1,613 lines · 20 tokens per session scan A 8bc0ccbb90aa
sp.reverse-engineer is a command published in the GitHub repository AbdullahMalik17/Voice-Assistant17 (11 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 12,246 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.