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/mercurialsolo/claudectl/braingit clone --depth 1 https://github.com/mercurialsolo/claudectlWhat 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.00016 | $0.00312 |
| Opus 5 | $0.00008 | $0.00156 |
| Sonnet 5 | $0.00003 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
brain 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
Control the claudectl brain's auto-approve/deny behavior for tool calls in this session.
Modes
on(default) — brain evaluates every tool call, auto-approves safe ones, denies dangerous ones. Low-confidence decisions fall through to normal permission prompts.off— brain is disabled. All tool calls go through Claude Code's normal permission flow. Use this when you want full manual control.auto— brain auto-approves all tool calls it considers safe, even with lower confidence. Use this when you trust the brain's judgment and want maximum speed.status— show the current mode without changing it.
What to do
Run claudectl --mode {{mode}} where {{mode}} is the argument the user provided (on, off, auto, or status). If no argument was provided, run claudectl --mode status.
After running the command, confirm the mode change to the user and briefly explain what it means:
off: "Brain disabled. Tool calls will go through normal permission prompts."on: "Brain active. Safe tool calls will be auto-approved, dangerous ones auto-denied."auto: "Brain in full auto mode. All decisions above the confidence threshold will execute without prompts."
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 · 24 lines · 16 tokens per session scan A 030807b5a59a
brain is a command published in the GitHub repository mercurialsolo/claudectl (197 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 312 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-30.
Other commands, from other repositories
blackboard
Read or write a Network-AI blackboard key (shared multi-agent state).
init
First-run teamctl onboarding — from no-teamctl-installed to a running supervised team in one conversation.
review-session-log
Use when the user asks what a session did, wants to review session history, or needs to find errors in a session log.
handoff
Create a model handoff using a single canonical handoff document and then validate it.
reflect
Capture a reflection after completing work — what was surprising, what should future agents know, what could improve.
bob-route
Preview which Bob mode a task id or a hypothetical description would route to.