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.
git clone --depth 1 https://github.com/YousefNabil-SOC/claude-apexWrote 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/yousefnabil-soc/claude-apex/map-codebase)<a href="https://agentmods.dev/commands/yousefnabil-soc/claude-apex/map-codebase"><img src="https://agentmods.dev/badge/commands/yousefnabil-soc/claude-apex/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/yousefnabil-soc/claude-apex/map-codebase"><img src="https://agentmods.dev/badge/commands/yousefnabil-soc/claude-apex/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 887039855655
gsd:map-codebase is a command published in the GitHub repository YousefNabil-SOC/claude-apex (3 stars, last pushed 4mo 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
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.
render
Inspect an archived transcript (gzipped) — show counts, tool calls, errors. Useful after a PreCompact or SessionEnd, before deciding to write a retroactive /continuum:checkpoint.
golden-path
The golden path. One command, idea to merged PR. Runs the full pipeline, prd → prp → plan → dev → test → pr, with sensor + eval gates at every stage.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.