Borrowing it
Nothing to install: this file belongs to GeoloeG-IsT/agents-reverse-engineer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GeoloeG-IsT/agents-reverse-engineer/main/.claude/commands/gsd/map-codebase.mdgit clone --depth 1 https://github.com/GeoloeG-IsT/agents-reverse-engineerWrote 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/geoloeg-ist/agents-reverse-engineer/map-codebase)<a href="https://agentmods.dev/commands/geoloeg-ist/agents-reverse-engineer/map-codebase"><img src="https://agentmods.dev/badge/commands/geoloeg-ist/agents-reverse-engineer/map-codebase/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/geoloeg-ist/agents-reverse-engineer/map-codebase"><img src="https://agentmods.dev/badge/commands/geoloeg-ist/agents-reverse-engineer/map-codebase.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.00022 | $0.00625 |
| Opus 5.5 | $0.00009 | $0.00250 |
| Sonnet 5.5 | $0.00004 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
gsd:map-codebase 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 1mo 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
97% identical to gsd:map-codebase — 8 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.
What it actually says
Each mapper agent explores a focus area and writes documents directly to .planning/codebase/. The orchestrator only receives confirmations, keeping context usage minimal.
Output: .planning/codebase/ folder with 7 structured documents about the codebase state.
<execution_context> @./.claude/get-shit-done/workflows/map-codebase.md </execution_context>
Load project state if exists: Check for .planning/STATE.md - loads context if project already initialized
This command can run:
- Before /gsd:new-project (brownfield codebases) - creates codebase map first
- After /gsd:new-project (greenfield codebases) - updates codebase map as code evolves
- Anytime to refresh codebase understanding
<when_to_use> Use map-codebase for:
- Brownfield projects before initialization (understand existing code first)
- Refreshing codebase map after significant changes
- Onboarding to an unfamiliar codebase
- Before major refactoring (understand current state)
- When STATE.md references outdated codebase info
Skip map-codebase for:
- Greenfield projects with no code yet (nothing to map)
- Trivial codebases (<5 files) </when_to_use>
<success_criteria>
- .planning/codebase/ directory created
- All 7 codebase documents written by mapper agents
- Documents follow template structure
- Parallel agents completed without errors
- User knows next steps </success_criteria>
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.
- 1mo ago First seen · 72 lines · 22 tokens per session scan A 7cb8cc0ce5c6
gsd:map-codebase is a command published in the GitHub repository GeoloeG-IsT/agents-reverse-engineer (22 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 625 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to gsd:map-codebase, differing in 8 lines, and is treated as a copy.
Other commands, from other repositories
review
Review an issue, PR, local patch, branch, or commit.
cross-review
../../workflows/cross-review.md.
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.
hatch3r-rework
User-guided rework planning for agent-implemented code in a fresh context window. Reconstructs what was delivered from the git diff, interviews the user for feedback, triages findings, validates them read-only against the code, and ends at a rework plan (docs/rework/) plus an execute-now-or-defer choice (copy-paste…
review
Deep code review command. Comprehensive code analysis across security, performance, and architecture.
debt-map
Technical debt mapping command. Systematically detects and prioritizes technical debt in the codebase.