What is agent-brain-list?

A command that lists Agent Brain servers running for different projects, including each project's address, process ID, operating mode, and health.

Use it to check running servers, include inactive instances with --all, or get JSON output for scripts.

It gives you one place to see which project servers are running and helps identify stale or unhealthy instances.

agent-brain-list — Command by SpillwaveSolutions

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-list

Clone the repo

git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 848 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.

Model	Per session	Once invoked
Fable 5	$0.00013	$0.00848
Opus 5	$0.00006	$0.00424
Sonnet 5	$0.00003	$0.00170
Haiku 4.5	$0.00001	$0.00085

Measured 2d ago against content hash 81f684bb2a11, 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-list 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 2d 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-list.md · 129 lines

How it starts

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

List Agent Brain Instances

Purpose

Displays all running Agent Brain server instances across all projects. Shows each instance's project name, URL, process ID, mode, and health status by scanning the global registry.

Usage

/agent-brain:agent-brain-list [--all] [--json]

Execution

Run the following command to list all instances:

agent-brain list

Options

agent-brain list              # List running instances only
agent-brain list --all        # Include stale/unhealthy instances
agent-brain list -a           # Short form of --all
agent-brain list --json       # Output as JSON for scripting

Expected Output

         Agent Brain Instances
Project         URL                      PID   Mode     Status
my-project      http://127.0.0.1:8000    12345 project  running
api-docs        http://127.0.0.1:8001    12678 project  running

2 running, 0 stale/unhealthy

JSON Output

agent-brain list --json

{
  "instances": [
    {
      "project_root": "/home/user/my-project",
      "project_name": "my-project",
      "base_url": "http://127.0.0.1:8000",
      "pid": 12345,
      "mode": "project",
      "status": "running",
      "started_at": "2026-01-31T10:30:00Z"
    }
  ],
  "total": 1
}

Output

Format the result as a table with the following columns:

Column	Description
Project	Project directory name
URL	Server base URL (e.g., `http://127.0.0.1:8000`)
PID	Process ID of the server
Mode	Instance mode: `project` or `shared`
Status	Health status: `running`, `unhealthy`, `stale`

Status Indicators

running: Server process is alive and health endpoint responds
unhealthy: Server process is alive but health endpoint fails
stale: Process is no longer alive (auto-cleaned from registry)

Registry Cleanup

Stale entries are automatically removed from the global registry when agent-brain list runs. By default, only running instances are shown. Use --all to include stale and unhealthy instances.

Read the full file on GitHub · 129 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.

2d ago First seen · 129 lines · 13 tokens per session scan A 81f684bb2a11

Subscribe to this mod's changes

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

Building agents

agent-brain-list