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 skills/brain-bootstrap/claude-code-brain-bootstrap/codebase-memorynpx skills add brain-bootstrap/claude-code-brain-bootstrap --skill codebase-memorygit clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrapWhat 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.00043 | $0.00631 |
| Opus 5 | $0.00022 | $0.00316 |
| Sonnet 5 | $0.00009 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
codebase-memory 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Memory — Structural Graph
Zero-file-read structural analysis. Always try these tools BEFORE reading files for structural questions.
Quick Decision Matrix
| Question | Tool |
|---|---|
What calls foo()? |
trace_path(function_name="foo", direction="inbound") |
What does foo() call? |
trace_path(function_name="foo", direction="outbound") |
| Full call chain | trace_path(direction="both", depth=3) |
| Impact of my change | detect_changes(base_branch="main") |
| Architecture overview | get_architecture |
| Find by name/pattern | search_graph(name_pattern="Auth.*") |
| Find by label | search_graph(label="Class") |
| Dead code | search_graph(max_degree=0, label="Function") |
| Custom query | query_graph(query="MATCH (n:Function)-[:CALLS]->(m) RETURN n.name, m.name LIMIT 20") |
| Execution flows | list_flows → get_affected_flows |
| ADR management | manage_adr(mode="get") |
Workflow — First Use
index_repository(repo_path=".")— first run only (~6s for 500 files)list_projects— verify indexedget_architecture— architecture map
Workflow — Before Reviewing Changes
detect_changes(base_branch="main")→ risk score + blast radiusget_affected_flows→ which execution paths breaktrace_pathon highest-risk functions
Workflow — Exploration
get_architecture→ community map, entry pointssearch_graph(name_pattern="<keyword>")→ find relevant nodestrace_path→ traverse from found nodesget_code_snippet(qualified_name="<name>")→ source with context
Known Gotchas
search_graph(relationship="HTTP_CALLS")filters by degree — usequery_graphfor actual edge inspectionquery_graphhas a 200-row cap — usesearch_graphwith degree filters for countstrace_pathrequires exact qualified names — usesearch_graph(name_pattern=...)firstdirection="outbound"misses cross-service callers — usedirection="both"- Results default to 10 per page — check
has_moreand paginate withoffset
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 · 61 lines · 43 tokens per session scan A 304743b786c8
codebase-memory is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 631 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 skills, from other repositories
implement
TRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/wip plan OR a standalone task (bug fix, GitHub issue, one-off change). Examples: "work on task 1", "fix this bug", "implement feature X from the issue". Provides structured execution with profile detection, dependency…
review-spec
Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.
chain-of-verification
Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
review-design
Review design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.
review-code
Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
dependency-handling
TRIGGER when: adding or upgrading any dependency — library, SDK, framework, API, IaC API version (K8s/Terraform/Helm), CRD, or container image. Use BEFORE writing the call. Forces context7/capy lookup instead of guessing.