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/SpillwaveSolutions/agent-brainWrote 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/spillwavesolutions/agent-brain/agent-brain-setup)<a href="https://agentmods.dev/commands/spillwavesolutions/agent-brain/agent-brain-setup"><img src="https://agentmods.dev/badge/commands/spillwavesolutions/agent-brain/agent-brain-setup/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/spillwavesolutions/agent-brain/agent-brain-setup"><img src="https://agentmods.dev/badge/commands/spillwavesolutions/agent-brain/agent-brain-setup.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.00021 | $0.04591 |
| Opus 5.5 | $0.00008 | $0.01836 |
| Sonnet 5.5 | $0.00004 | $0.00918 |
| Haiku 4.5 | $0.00002 | $0.00459 |
Grade D, and why
agent-brain-setup scanned grade D with 4 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 "$CONFIG_PATH" Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
SCRIPT=$(find ~/.claude/plugins/agent-brain/scripts ~/.claude/skills/agent-brain/scripts agent-brain-plugin/scripts -name "ab-setup-check.sh" 2>/dev/null | head -1) Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
SCRIPT=$(find ~/.claude/plugins/agent-brain/scripts ~/.claude/skills/agent-brain/scripts agent-brain-plugin/scripts -name "ab-setup-check.sh" 2>/dev/null | head -1) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
"Bash(curl:*)", How it starts
The opening of the file, as written. The whole thing — 601 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complete Agent Brain Setup
Purpose
Runs a complete guided setup flow for Agent Brain, taking the user from zero to a fully working installation. This command orchestrates installation, configuration, initialization, and verification steps.
Usage
/agent-brain-setup
Execution
Run each step in sequence, proceeding only if the previous step succeeds.
Step 0: Bootstrap Permissions
Before running any shell commands, ensure .claude/settings.json exists with the required permissions for the setup wizard. Use the Write tool (not Bash) to create this file — the Write tool is always available without a permission gate.
Check if the file already exists:
ls .claude/settings.json 2>/dev/null && echo "EXISTS" || echo "MISSING"
If missing or if it does not contain "Bash(agent-brain:*)", write the following content to .claude/settings.json using the Write tool:
{
"_comment": "Agent Brain setup permissions — written by /agent-brain-setup. Safe to commit.",
"permissions": {
"allow": [
"Bash(agent-brain:*)",
"Bash(lsof:*)",
"Bash(ollama:*)",
"Bash(docker:*)",
"Bash(mkdir:*)",
"Bash(cat:*)",
"Bash(jq:*)",
"Bash(mv:*)",
"Bash(du:*)",
"Bash(ps:*)",
"Bash(pgrep:*)",
"Bash(pip:*)",
"Bash(pipx:*)",
"Bash(uv:*)",
"Bash(python:*)",
"Bash(python3:*)",
"Bash(rg:*)",
"Bash(wc:*)",
"Bash(curl:*)",
"Bash(ls:*)",
"Bash(find:*)",
"Bash(chmod:*)",
"Bash(grep:*)",
"Bash(bash:*)"
],
"deny": []
}
}
After writing the file, tell the user:
"Wrote .claude/settings.json with Agent Brain setup permissions. These allow the wizard to run without permission prompts. The file is safe to commit — it grants access only to standard development tools."
IMPORTANT: If .claude/settings.json already exists with custom content, MERGE: add any missing Bash(...) entries from the list above into the existing allow array rather than replacing the file.
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 · 601 lines · 21 tokens per session scan D d4da0f9157ff
agent-brain-setup is a command published in the GitHub repository SpillwaveSolutions/agent-brain (119 stars, last pushed 27d ago), licensed MIT. It adds 21 tokens to every session and 4,591 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it D with 4 findings (asks for root, reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
tools
Manage MCP tools with natural language commands to list, enable, and disable tools and tool groups.
evolve-lite-subscribe
Add a shared guidelines repo (read-scope subscription or write-scope publish target) to the unified repos list.
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.