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/dilawarshafiq/unworldly/sp.reverse-engineergit clone --depth 1 https://github.com/DilawarShafiq/unworldlyWrote 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/dilawarshafiq/unworldly/sp.reverse-engineer)<a href="https://agentmods.dev/commands/dilawarshafiq/unworldly/sp.reverse-engineer"><img src="https://agentmods.dev/badge/commands/dilawarshafiq/unworldly/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.12179 |
| Opus 5 | $0.00010 | $0.06090 |
| Sonnet 5 | $0.00004 | $0.02436 |
| Haiku 4.5 | $0.00002 | $0.01218 |
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 3d 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 This is a copy
100% identical to sp.reverse-engineer — 2,806 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 — 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"
Step 1.2: Discover Entry Points
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.
- 3d ago First seen · 1,613 lines · 20 tokens per session scan A cb3985b31172
sp.reverse-engineer is a command published in the GitHub repository DilawarShafiq/unworldly (9 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 12,179 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to sp.reverse-engineer, differing in 2,806 lines, and is treated as a copy.
Other commands, from other repositories
aod.project-plan
Create implementation plan with dual sign-off (PM + Architect) - Streamlined v2.
audit_docs
Audit all project metadata files for stale counts, version mismatches, broken references, and missing entries. Reports discrepancies without auto-fixing.
submit_to_list
Fork an external GitHub repo, add an entry to a curated list (e.g. awesome-), and open a PR — all via gh CLI.
aod.blueprint
Unified project setup & story generation — auto-detects new vs existing projects.
capture-feedback
Quick feedback capture with structured signals.
doctor
Run procedural readiness checks for goal-flight.