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/spillwavesolutions/agent-brain/agent-brain-verifygit clone --depth 1 https://github.com/SpillwaveSolutions/agent-brainWhat 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.00012 | $0.01413 |
| Opus 5 | $0.00006 | $0.00707 |
| Sonnet 5 | $0.00002 | $0.00283 |
| Haiku 4.5 | $0.00001 | $0.00141 |
Grade A, and why
agent-brain-verify 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 3d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Agent Brain Setup
Purpose
Performs a comprehensive verification of the Agent Brain installation, checking that all components are properly installed, configured, and functioning. This is a plugin-level workflow that runs multiple CLI commands to produce a consolidated health check report.
Usage
/agent-brain:agent-brain-verify
Execution
Run the following verification steps in sequence:
Step 1: Check Package Installation
agent-brain --version
python -c "import agent_brain_cli; print(agent_brain_cli.__version__)" 2>/dev/null
python -c "import agent_brain_server; print(agent_brain_server.__version__)" 2>/dev/null
Step 2: Check Python Version
python --version
Step 3: Check Provider Configuration
# Show active provider config
agent-brain config show 2>/dev/null || echo "Config not available"
Step 4: Check Project Initialization
ls -la .agent-brain/config.json 2>/dev/null
Step 5: Check Server Status (if running)
agent-brain status
Step 6: Run Health Check (if server running)
agent-brain status --json 2>/dev/null || echo "Server not running"
Output
All Checks Passing
Agent Brain Verification
========================
Installation
------------
[OK] agent-brain-cli: 1.2.0
[OK] agent-brain-rag: 1.2.0
[OK] Python: 3.11.4 (>= 3.10 required)
Configuration
-------------
[OK] OPENAI_API_KEY: Set
[OK] ANTHROPIC_API_KEY: Set (optional)
Project Setup
-------------
[OK] Project initialized: .agent-brain/
[OK] Config file: .agent-brain/config.json
Server Status
-------------
[OK] Server running on port 49321
[OK] Health: healthy
[OK] Documents indexed: 150
[OK] Chunks: 750
Verification Complete!
======================
All checks passed. Agent Brain is ready to use.
Quick commands:
Search: /agent-brain:agent-brain-search "your query"
Index: /agent-brain:agent-brain-index /path/to/docs
Status: /agent-brain:agent-brain-status
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.
- 3d ago First seen · 287 lines · 12 tokens per session scan A e010a6ccdaf1
agent-brain-verify is a command published in the GitHub repository SpillwaveSolutions/agent-brain (117 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 1,413 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
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.