serve

A command that starts basemind as an MCP server using standard input and output for JSON messages. An MCP server lets an AI client discover and call tools.

In plain words
What is it for?
Use it with an MCP client or REPL to test JSON-RPC requests, list tools, and inspect tool schemas; automated integrations should use the configured MCP entry.
Why use it?
It provides a direct way to manually test the server and inspect its available tools and input schemas.

Command

Part of the basemind plugin — 15 skills, 10 commands, 6 agents, 2 hooks, 1 MCP server shipped together

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/goldziher/basemind/serve
Clone the repo
git clone --depth 1 https://github.com/Goldziher/basemind

Or install basemind, the plugin that ships this one along with the rest of its 15 skills, 10 commands, 6 agents, 2 hooks, 1 MCP server.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 179 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.00009 $0.00179
Opus 5 $0.00005 $0.00089
Sonnet 5 $0.00002 $0.00036
Haiku 4.5 $0.00001 $0.00018

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

Security

Grade A, and why

serve 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.

.ai-rulez/commands/serve.md · 21 lines

What it actually says

Serve

Start the basemind MCP stdio server. Useful when manually testing tools via a client like mcp-cli or the rmcp REPL.

  1. Build if stale: cargo build --release.

  2. Run:

    ./target/release/basemind serve
    
  3. The server reads MCP JSON-RPC over stdin and writes responses to stdout. Tool list available via tools/list; per-tool schemas via tools/list + the schema field.

For automated AI-tool integration, prefer the basemind entry in .mcp.jsonai-rulez generate writes it from the [[mcp_servers]] block in .ai-rulez/config.toml.

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 · 21 lines · 9 tokens per session scan A 3aa25bdf3db5

Subscribe to this mod's changes

serve is a command published in the GitHub repository Goldziher/basemind (91 stars, last pushed 7d ago), licensed MIT. It adds 9 tokens to every session and 179 once invoked, about $0.0000 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.