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/brain-bootstrap/claude-code-brain-bootstrapWrote 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/brain-bootstrap/claude-code-brain-bootstrap/ask)<a href="https://agentmods.dev/commands/brain-bootstrap/claude-code-brain-bootstrap/ask"><img src="https://agentmods.dev/badge/commands/brain-bootstrap/claude-code-brain-bootstrap/ask/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/brain-bootstrap/claude-code-brain-bootstrap/ask"><img src="https://agentmods.dev/badge/commands/brain-bootstrap/claude-code-brain-bootstrap/ask.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.00017 | $0.00466 |
| Opus 5.5 | $0.00007 | $0.00186 |
| Sonnet 5.5 | $0.00003 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
ask 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.
What it actually says
Codebase Question Router
Answer this question about the codebase: $ARGUMENTS
Route to the right tool based on question type. Don't search files manually when a smarter tool exists.
Routing rules
Classify the question and use the corresponding tool:
Architecture / flow / how does X work / trace a call
Use mcp__codebase-memory-mcp__trace_path or mcp__codebase-memory-mcp__get_architecture.
Also read graphify-out/GRAPH_REPORT.md if it exists — it contains god nodes, community structure,
and surprising cross-module connections already analyzed.
Find / search / locate / what file / which function
Use mcp__cocoindex-code__search with a semantic query.
This finds code by meaning, not exact text — useful when you don't know the exact name.
Safe to change / impact / blast radius / what breaks / risk score / dependencies
Use mcp__code-review-graph__detect_changes_tool with base_branch="main".
Reports: risk score 0–100, blast radius (files affected), breaking changes, dependent modules.
General code question (no plugin available / question is narrow / specific file)
Read the file directly. Grep for the symbol. Don't over-route simple questions.
Decision logic
- If $ARGUMENTS contains architecture/flow/trace/how/explain → codebase-memory-mcp + graphify
- If $ARGUMENTS contains find/search/locate/where/what file → cocoindex
- If $ARGUMENTS contains safe/impact/blast/breaks/risk/change/affect → code-review-graph
- If none match → read directly, use Grep/Glob
Answer format
Give a direct, concise answer. Include:
- The tool used and why
- The finding (file path + line if applicable)
- Any surprising connections the graph revealed (if applicable)
If the question cannot be answered from graph/search alone, fall back to reading the relevant files.
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 · 48 lines · 17 tokens per session scan A 3ef48f152891
ask is a command published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 466 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
restart
Restart the Claude Mnemonic worker process.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.