status

A command that reports the health and connection state of the Evolver system. It can show whether its proxy or MCP connection, local evolution memory, workspace, and full engine are available.

In plain words
What is it for?
Use it to check Evolver connectivity, synchronization queues, registration status, local memory, workspace details, and whether the full engine is installed.
Why use it?
It gives a short status report instead of making you inspect several connection and memory checks yourself. It also explains pending account connection and credit-related problems in plain language.

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/evomap/evolver-claude-code-plugin/status
Clone the repo
git clone --depth 1 https://github.com/EvoMap/evolver-claude-code-plugin
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 636 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.00024 $0.00636
Opus 5 $0.00012 $0.00318
Sonnet 5 $0.00005 $0.00127
Haiku 4.5 $0.00002 $0.00064

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

Security

Grade A, and why

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

commands/status.md · 50 lines

What it actually says

Report Evolver health as a short checklist.

  1. Proxy / MCP — call the evolver_status MCP tool (from the evolver-proxy server). If it returns status, show node_id, outbound_pending, inbound_pending, last_sync_at. If it errors, the Proxy is down — note it starts when you run evolver once in a git repo, and that the local memory hooks keep working regardless.

    Then translate the Proxy state into plain "are you connected?" language for the user — don't dump raw error JSON or internal terms like node_secret, stake, or hub_rotate:

    • If ~/.evomap/claim_url exists, the node is registered but not yet claimed. Tell the user to sign in to evomap.ai and open that URL to finish connecting — that's the only step, with no id or secret to find.

      [ -f ~/.evomap/claim_url ] && echo "not yet connected — sign in to evomap.ai and open: $(cat ~/.evomap/claim_url)" || echo "no pending claim link"
      
    • If a network call reports insufficient credits / HTTP 402, say plainly that the network features need credits (buy or subscribe at https://evomap.ai/pricing); local memory keeps working as usual.

  2. Evolution memory — does the local graph exist and how many outcomes?

F=~/.evolver/memory/evolution/memory_graph.jsonl
[ -f "$F" ] && echo "memory graph: $F ($(wc -l < "$F" | tr -d ' ') outcomes)" || echo "no local evolution memory yet (appears after a session ends with changes in a git repo)"
  1. This workspace's id — the forge-resistant scoping key (only in a git repo):
R=$(git rev-parse --show-toplevel 2>/dev/null); [ -n "$R" ] && { [ -f "$R/.evolver/workspace-id" ] && echo "workspace-id: present" || echo "workspace-id: not yet created"; } || echo "not a git repo — memory inactive here"
  1. Full engine (optional) — is the @evomap/evolver CLI installed?
command -v evolver >/dev/null 2>&1 && evolver --version 2>/dev/null | head -1 || echo "evolver CLI not installed — hooks + MCP still work; 'npm i -g @evomap/evolver' unlocks /evolver:run etc."

Finish with one line on overall readiness.

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. 2d ago First seen · 50 lines · 24 tokens per session scan A a186c913a478

Subscribe to this mod's changes

status is a command published in the GitHub repository EvoMap/evolver-claude-code-plugin (12 stars, last pushed 12d ago), licensed MIT. It adds 24 tokens to every session and 636 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.