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-init)<a href="https://agentmods.dev/commands/spillwavesolutions/agent-brain/agent-brain-init"><img src="https://agentmods.dev/badge/commands/spillwavesolutions/agent-brain/agent-brain-init/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-init"><img src="https://agentmods.dev/badge/commands/spillwavesolutions/agent-brain/agent-brain-init.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.00012 | $0.01622 |
| Opus 5.5 | $0.00005 | $0.00649 |
| Sonnet 5.5 | $0.00002 | $0.00324 |
| Haiku 4.5 | $0.00001 | $0.00162 |
Grade C, and why
agent-brain-init scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Reset with: rm -rf .agent-brain && agent-brain init How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Agent Brain Project
Purpose
Initializes the current project for Agent Brain by creating the necessary configuration directory and files. This sets up per-project isolation, allowing each project to have its own Agent Brain instance with separate configuration and data.
Usage
/agent-brain:agent-brain-init [--path <path>] [--host <host>] [--port <port>] [--force] [--state-dir <dir>] [--json]
Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
| --path / -p | No | Auto-detect | Project path (auto-detects git root or project markers) |
| --host | No | 127.0.0.1 | Server bind host |
| --port | No | Auto-select | Preferred server port (disables auto-port if set) |
| --force / -f | No | false | Overwrite existing configuration |
| --state-dir / -s | No | .agent-brain | Custom state directory for index data |
| --json | No | false | Output as JSON |
Examples
/agent-brain:agent-brain-init
/agent-brain:agent-brain-init --path /my/project
/agent-brain:agent-brain-init --port 8080
/agent-brain:agent-brain-init --state-dir /custom/path
/agent-brain:agent-brain-init --force
Execution
Run Initialization
agent-brain init
agent-brain init --path /my/project
agent-brain init --port 8080
agent-brain init --state-dir /custom/path
agent-brain init --force
This creates the .agent-brain/ directory structure in the project root.
Verify Initialization
ls -la .agent-brain/
Output
Agent Brain Initialization
==========================
Initializing Agent Brain for current project...
Running: agent-brain init
Created directory structure:
.agent-brain/
config.json - Project configuration
chroma_db/ - Vector store (created on first index)
bm25_index/ - Keyword index (created on first index)
Project initialized successfully!
Configuration file: .agent-brain/config.json
{
"project_name": "my-project",
"created_at": "2025-01-31T12:00:00Z",
"mode": "project"
}
Next steps:
1. Start server: /agent-brain:agent-brain-start
2. Index documents: /agent-brain:agent-brain-index ./docs
3. Search: /agent-brain:agent-brain-search "your query"
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 · 269 lines · 12 tokens per session scan C 20c943df7eda
agent-brain-init is a command published in the GitHub repository SpillwaveSolutions/agent-brain (119 stars, last pushed 27d ago), licensed MIT. It adds 12 tokens to every session and 1,622 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
mempalace-status
Show the current state of your memory palace — wings, rooms, drawer counts, and suggestions.
tree-ring-update
Check for or install a verified Tree Ring Memory CLI update without changing installation scope.
tree-ring-recall
Recall durable Tree Ring Memory context before starting or resuming work.
tree-ring-status
Check receipt-backed Tree Ring harness readiness without claiming configuration is activation.
forget
Delete a memory from memini.
engram-graph
Traverse the knowledge graph from a seed — searchbyrelation + visualize.