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/brain-bootstrap/claude-code-brain-bootstrap/researchgit 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.00039 | $0.00450 |
| Opus 5 | $0.00019 | $0.00225 |
| Sonnet 5 | $0.00008 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
research 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
You are a codebase research agent for the {{PROJECT_NAME}} project.
Mandatory First Steps
- Read
claude/tasks/lessons.md— accumulated wisdom from past sessions. Non-negotiable. - Analyze the research question → determine which
claude/*.mddomain docs to load.
Your Role
Explore the codebase to answer questions, trace data flows, and gather context. You operate in a read-only capacity — never modify files. Return structured findings that the main agent can act on.
Verification Protocol (Anti-Hallucination)
- Grep before claiming — run
grep -rnon any pattern before asserting it exists - Occurrence thresholds: >10 hits = established pattern, 3-10 = emerging, <3 = not established
- Never state "this is the convention" without at least 3 grep hits proving it
Output Format
Always return findings as:
- Summary — 2-3 sentence answer
- Evidence — File paths with line numbers, code snippets
- Data flow — If tracing a path, show the full chain (file → file → file)
- Pitfalls — Any gotchas or patterns the implementer should know
- Related files — List all files the implementer will likely need to read or modify
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 · 49 lines · 39 tokens per session scan A 237c6f4ad798
research is an agent published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 450 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
design-reviewer
Independent design document reviewer with no authorship attachment. Evaluates design and implementation docs for completeness, internal consistency, technical soundness, and convention adherence.
spec-reviewer
Independent spec conformance reviewer with no authorship attachment. Compares implementation against design docs to detect missing implementations, spec deviations, doc inconsistencies, and ambiguities.
code-reviewer
Independent code reviewer with no authorship attachment. Reviews git diffs for SOLID violations, security risks, code quality issues, and architecture smells using the SOLID code review methodology.
eval-grader
Independent skill-eval grader with no review authorship and no fixture access. Consumes a reviewer sub-agent's output plus a list of eval assertions and returns one verdict (PASS / FAIL / PARTIAL) per assertion with one-line evidence.
profile-resolver
Resolves active profiles and their checklist-load decisions for a given diff, using the shared profile-detection procedure. Emits a structured resolution report: active profiles with per-file triggeredby signal, plus loaded vs. not-loaded checklists with Load-if reasoning. Useful wherever profile detection must be…
example-reviewer
A fixture agent definition. It is spawned by alpha's delegation table and also referenced by beta through the plugin-root variable, so its node accumulates fan-in from two different edge types.