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 commands/0xchamin/brain-kit/researchgit clone --depth 1 https://github.com/0xchamin/brain-kitWhat 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.00018 | $0.00853 |
| Opus 5 | $0.00009 | $0.00426 |
| Sonnet 5 | $0.00004 | $0.00171 |
| Haiku 4.5 | $0.00002 | $0.00085 |
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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/research - deep research (external evidence)
The contract is AGENTS.md § "Deep research on request". Read it now and follow it - this file
is only the Claude Code wrapper for that stage. Do not duplicate the contract here; if the two ever
disagree, AGENTS.md wins.
Adopt fact-checker + synthesizer (+ mentor if the goal is teaching the concept).
Target
$ARGUMENTS
If that names a source folder, research that source's gated nodes. If it names a topic or a bare
question, research that - but still land the output in a context/ note under the most relevant
source, or in reports/ if it spans several.
Run it
- Orient. Read the source's
SOURCE.mdandnodes.md. Pick the research targets by ID:single-legnodes, anythingneeds-check, recorded divergences, and theLEARNING.mdopen questions. Target claims, not the subject - open-ended topic research makes you a summarizer. - Read the brain before the web.
grepthe rootINDEX.md,brain/topics/*.mdandbrain/claims.md. A prior source may already answer this; that link beats a fresh fetch. - Search and fetch, favouring T1-T3 (see the tier table in
AGENTS.md). Deliberately attempt the cross-domain hop - the established name for this idea in an older discipline. Respect the budget: ≤ 8 searches, ≤ 12 fetches; stop early on two independent agreeing sources, or when a pass surfaces nothing new. - Apply the independence rule. A companion repo, a vendor blog restating that vendor's own talk, or same-lab work is the same leg wearing a different hat: record it, cite it, but do not raise confidence.
- Write
sources/<id>/context/<NN>_<slug>.mdusing the structure insources/_TEMPLATE/context/README.md. Every finding gets a verdict (supports/contradicts/refines/no-evidence), a tier, and an independence call. End with a Confidence assessment - never interrupt with clarifying questions; state assumptions there instead. - Feed it back in the same pass: update node confidences in
nodes.md(pointing at the context note), cite external support inbrain/claims.md, add terms tobrain/glossary.md, setSOURCE.mdStatus, and append tobrain/log.md. Keep external findings out ofLEARNING.md's body - it may cite the note, never absorb it. - Report back: one paragraph on what changed - which claims got stronger, which got weaker,
which found nothing - then
git diff.
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 · 60 lines · 18 tokens per session scan A bc026d9b36b5
research is a command published in the GitHub repository 0xchamin/brain-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 853 once invoked, about $0.0001 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.