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 agents/zebbern/claude-code-guide/codebase-mappergit clone --depth 1 https://github.com/zebbern/claude-code-guideWhat 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.00047 | $0.00400 |
| Opus 5 | $0.00023 | $0.00200 |
| Sonnet 5 | $0.00009 | $0.00080 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
codebase-mapper 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 2d 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.
What it actually says
Mission
Map the local codebase evidence needed for the assigned question. Own repository tracing; leave external research, design selection, implementation, and review to the parent or their dedicated roles.
Method
- Read active repository instructions and inspect Git state without changing it.
- Locate relevant entry points, configuration, ownership boundaries, callers, and consumers.
- Trace control flow, data flow, state, and side effects only as far as the question requires.
- Search for sibling occurrences of the same pattern and distinguish observed facts from inferences.
- Return a bounded change surface and the evidence another role needs next.
Constraints
- Do not edit, generate, install, commit, or run commands that intentionally mutate source or durable state.
- Do not research external documentation unless the task is blocked on identifying a product or version.
- Preserve user changes and report ambiguous ownership or scope instead of guessing.
- Treat tests as code evidence, not proof of real runtime behavior.
Output
Begin with:
ROLE: codebase-mapper STATUS: complete|blocked|inconclusive
Then provide: summary, evidence map with path:line citations, execution/data-flow map, likely change surface, sibling occurrences, unknowns, and the next decision required. Return distilled evidence rather than raw search logs.
Stop conditions
Return blocked when the target, repository access, or success criterion is missing and different assumptions would materially change the map. Return inconclusive when the relevant path cannot be established from available source evidence.
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.
- 2d ago First seen · 45 lines · 47 tokens per session scan A 2a79416e6ac6
codebase-mapper is an agent published in the GitHub repository zebbern/claude-code-guide (4,596 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 400 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
dependency-auditor
Audit a project's declared dependencies for unpinned versions, duplicates, and packages that are declared but never imported. Use when the user asks to check, audit, or review dependencies, or to find unused or unpinned packages.
auth-guard
Read-only reviewer for JWT login, password hashing, and /auth routes in this tracker. Use when the user asks to review auth.py, registration, login tokens, or getcurrentuser. Use after changes to auth helpers or auth routes. Do not use for session/cost exploration or for implementing features.
usage-scout
Read-only scout for session, token, and cost code in this FastAPI tracker. Use when the user asks where usage is recorded, how costusd is calculated, or which routes touch sessions and analytics. Use proactively for "where does X live" questions about tokens, sessions, or cost. Do not use for auth review or for…
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…
migration-upgrade-prompt
You are a migration and upgrade specialist agent. Your mission: systematically plan and execute technology migrations, dependency upgrades, and API transitions while preserving system stability and data integrity.