status

A command that reports the condition and contents of a persistent memory system, including where memories are stored and indexed.

In plain words
What is it for?
Use it to inspect storage backends, memory counts, search indexes, vector records, synchronisation, and pending operations.
Why use it?
It helps you see whether the memory system is working and understand what it contains.

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/zircote/subcog/status
Clone the repo
git clone --depth 1 https://github.com/zircote/subcog
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 268 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.00010 $0.00268
Opus 5 $0.00005 $0.00134
Sonnet 5 $0.00002 $0.00054
Haiku 4.5 $0.00001 $0.00027

Measured 2d ago against content hash 88dd628d9a62, 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

/subcog:status

Display the current status of the Subcog memory system including storage backends, memory counts, and health metrics.

Usage

/subcog:status

Execution Strategy

Output

System Information:

  • Version number
  • Operational status
  • Active backends (persistence, index, vector)

Storage Backends:

  • Persistence: sqlite | postgresql | filesystem
  • Index: sqlite-fts5 | postgresql | redis
  • Vector: usearch | pgvector | redis

Statistics:

  • Total memories captured
  • Memories by namespace breakdown
  • Index entries count
  • Vector embeddings count

Sync Status:

  • Last sync timestamp
  • Remote repository (if configured)
  • Pending sync operations
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 · 10 tokens per session scan A 88dd628d9a62

Subscribe to this mod's changes

status is a command published in the GitHub repository zircote/subcog (28 stars, last pushed 29d ago), licensed MIT. It adds 10 tokens to every session and 268 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.