agent-brain-status

A command that reports whether the Agent Brain search server is running and how much content it has indexed. The index is the searchable catalogue of documents split into smaller sections for retrieval.

In plain words
What is it for?
It is used to troubleshoot search setup, inspect indexed folders and document counts, monitor indexing, and obtain machine-readable status with JSON output.
Why use it?
It lets you check server health, indexing progress, watched folders, cached embeddings, and optional graph-index status before running searches.

Command

Install

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.

agentmods
npx agentmods add commands/spillwavesolutions/agent-brain/agent-brain-status
Clone the repo
git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,211 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.01211
Opus 5 $0.00010 $0.00606
Sonnet 5 $0.00004 $0.00242
Haiku 4.5 $0.00002 $0.00121

Measured 3d ago against content hash 082d4b22e442, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-brain-status 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.

agent-brain-plugin/commands/agent-brain-status.md · 227 lines

How it starts

The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Brain Status

Purpose

Displays the current status of the Agent Brain server, including:

  • Server health and version
  • Document and chunk counts
  • Indexing progress (if in progress)
  • Indexed folders list
  • File watcher status
  • Embedding cache statistics
  • Graph index status (if enabled)

Use this command to verify the server is running before performing searches.

Usage

/agent-brain:agent-brain-status [--url <url>] [--json] [--verbose]

Parameters

Parameter Required Default Description
--url No from config or http://127.0.0.1:8000 Server URL (env: AGENT_BRAIN_URL)
--json No false Output in JSON format for scripting
--verbose, -v No false Show additional detail (cache size, memory stats)

Execution

Basic Status Check

agent-brain status

Verbose Status

agent-brain status --verbose

JSON Output

agent-brain status --json

Output

Human-Readable Format

          Server Status
           HEALTHY

Metric             Value
Server Version     9.0.0
Total Documents    142
Total Chunks       750
Indexing           Idle
Indexed Folders    ./docs
                   ./src
File Watcher       running (2 watched folder(s))
Embedding Cache    1,200 entries, 85.3% hit rate (1,024 hits, 176 misses)
Graph Index        Enabled - 45 entities, 120 rels

JSON Format

{
  "health": {
    "status": "healthy",
    "message": "Server is running",
    "version": "9.0.0"
  },
  "indexing": {
    "total_documents": 142,
    "total_chunks": 750,
    "indexing_in_progress": false,
    "progress_percent": 0.0,
    "indexed_folders": ["./docs", "./src"],
    "file_watcher": {
      "running": true,
      "watched_folders": 2
    },
    "embedding_cache": {
      "entry_count": 1200,
      "hit_rate": 0.853,
      "hits": 1024,
      "misses": 176
    }
  }
}

Status Indicators

Status Meaning
healthy Server running and responsive
unhealthy Server running but issues detected
not_running Server not started
indexing Currently indexing documents
idle Ready for queries

Read the full file on GitHub · 227 lines

Changes

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.

  1. 3d ago First seen · 227 lines · 19 tokens per session scan A 082d4b22e442

Subscribe to this mod's changes

agent-brain-status is a command published in the GitHub repository SpillwaveSolutions/agent-brain (117 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 1,211 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.