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-graph)<a href="https://agentmods.dev/commands/spillwavesolutions/agent-brain/agent-brain-graph"><img src="https://agentmods.dev/badge/commands/spillwavesolutions/agent-brain/agent-brain-graph/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-graph"><img src="https://agentmods.dev/badge/commands/spillwavesolutions/agent-brain/agent-brain-graph.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.00016 | $0.01648 |
| Opus 5.5 | $0.00006 | $0.00659 |
| Sonnet 5.5 | $0.00003 | $0.00330 |
| Haiku 4.5 | $0.00002 | $0.00165 |
Grade A, and why
agent-brain-graph 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 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.
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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Brain Graph Search
Purpose
Performs GraphRAG-powered search for relationship and dependency queries. This mode queries the knowledge graph to find entities (functions, classes, modules) and their relationships (calls, imports, inherits).
Graph search is ideal for:
- Finding what calls a specific function
- Exploring class inheritance hierarchies
- Understanding module dependencies
- Tracing data flow through code
Usage
/agent-brain:agent-brain-graph <query> [--top-k <n>] [--threshold <t>]
Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
| query | Yes | - | The relationship or dependency query |
| --top-k | No | 5 | Number of results (1-20) |
| --threshold | No | 0.3 | Minimum similarity threshold (0.0-1.0) |
Prerequisites
GraphRAG must be enabled before using graph search:
# Enable graph indexing
export ENABLE_GRAPH_INDEX=true
export GRAPH_STORE_TYPE=simple # or kuzu
export GRAPH_USE_CODE_METADATA=true
export GRAPH_USE_LLM_EXTRACTION=true
# Optional dependencies
pip install "agent-brain-rag[graphrag]" # LLM extractor
pip install "agent-brain-rag[graphrag-kuzu]" # Kuzu backend
# Start server
agent-brain start
# Rebuild index with graph extraction
agent-brain index /path/to/code --rebuild
Check Graph Status
agent-brain status
# Look for: Graph Index: enabled (X entities, Y relationships)
Backend Requirements
Graph search is only available when using the ChromaDB storage backend (default). If you are using the PostgreSQL backend (AGENT_BRAIN_STORAGE_BACKEND=postgres), graph queries will return an error:
Error: Graph queries (mode='graph') require ChromaDB backend.
Current backend: 'postgres'.
To use graph queries, set AGENT_BRAIN_STORAGE_BACKEND=chroma.
To use graph search, switch to ChromaDB backend or use /agent-brain:agent-brain-hybrid for hybrid BM25 + vector search on any backend.
Execution
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 · 259 lines · 16 tokens per session scan A e9874e0f6a1c
agent-brain-graph is a command published in the GitHub repository SpillwaveSolutions/agent-brain (119 stars, last pushed 27d ago), licensed MIT. It adds 16 tokens to every session and 1,648 once invoked, about $0.0001 per session on Opus 5.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
cleaning
A command for inspecting and safely cleaning a project or an entire server, including unused code, duplicates, conflicts, and leftover files.
bottleneck-detect
Analyze performance bottlenecks in swarm operations and suggest optimizations.
optimizer
Performance optimization with systematic analysis and improvements.
modernize-assess
Full discovery & portfolio analysis of a legacy system — inventory, complexity, debt, relative scale.
modernize-map
Dependency & topology mapping — call graphs, data lineage, batch flows, rendered as navigable diagrams.
checklist
Generate a custom checklist for the current feature based on user requirements.