memory-status

memory-status is a command for Claude Code from Pseudogiant-xr/Pseudolife-MCP. It costs 14 tokens per session (735 once invoked), scanned A, original, Apache-2.0.

A command that checks the health and stored-data status of the Pseudolife-MCP memory service, including its consolidation process.

In plain words
What is it for?
Use it to inspect memory counts, capacity, dropped data, reference documents, communities, and pending consolidation work.
Why use it?
It shows whether the memory service is running, under capacity pressure, or reporting a failed component. It also points to the startup command if the service is down.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the pseudolife-memory plugin — 2 commands, 7 hooks shipped together

Good fit Use it to inspect memory counts, capacity, dropped data, reference documents, communities, and pending consolidation work.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/pseudogiant-xr/pseudolife-mcp/memory-status
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.

Clone the repo
git clone --depth 1 https://github.com/Pseudogiant-xr/Pseudolife-MCP

Made for: Claude Code.

Or install pseudolife-memory, the plugin that ships this one along with the rest of its 2 commands, 7 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for memory-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/pseudogiant-xr/pseudolife-mcp/memory-status/github.svg)](https://agentmods.dev/commands/pseudogiant-xr/pseudolife-mcp/memory-status)
Your own site
<a href="https://agentmods.dev/commands/pseudogiant-xr/pseudolife-mcp/memory-status"><img src="https://agentmods.dev/badge/commands/pseudogiant-xr/pseudolife-mcp/memory-status/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for memory-status

Your own site · 80×15
<a href="https://agentmods.dev/commands/pseudogiant-xr/pseudolife-mcp/memory-status"><img src="https://agentmods.dev/badge/commands/pseudogiant-xr/pseudolife-mcp/memory-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 735 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00014 $0.00735
Opus 5.5 $0.00006 $0.00294
Sonnet 5.5 $0.00003 $0.00147
Haiku 4.5 $0.00001 $0.00073

Measured 22d ago against content hash 6cf794157308, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

memory-status scanned grade A with 1 finding 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 22d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

1. Fetch `http://127.0.0.1:8765/health` (curl or WebFetch). If it fails,
plugin/commands/memory-status.md · 47 lines

What it actually says

Report the state of the Pseudolife memory stack:

memory_stats needs the core tool tier and memory_dream the full one: if your client does not list them, call memory_toolset(action="expand") (one tier per call) until it reports current: "full", then rediscover tools.

  1. Fetch http://127.0.0.1:8765/health (curl or WebFetch). If it fails, report that the daemon is down and how to start it: docker compose -f <clone>/ops/docker-compose.yml up -d (install guide: https://github.com/Pseudogiant-xr/Pseudolife-MCP#quickstart).
  2. Call memory_stats() and summarize: total_memories, store occupancy as a capacity meter (bands[0].size / capacity under the default flat preset — multi-band presets get a per-band table instead), the preset, and capacity pressure. A non-null capacity_warning means the store is within 20% of the point where every new memory permanently deletes an old one: lead the report with its message. true_drops_total counts those deletions all-time (last_true_drop names the most recent; true_drops counts only since the daemon started) — flag any non-zero. Then the reference bank (reference_bank_size / reference_document_count), and communities. Flag weights_reset: true if present — it means the store's counters restarted fresh. If read_audit is present, note its entries.never_read_pct as a coverage signal — the old-and-unread tail, not the young entries that are expected to be unread yet.
  3. Call memory_dream(action="status") for consolidation state: backlog, idle_seconds, would_fire, and any pending outcome inference. backlog is what is still pending; dream_cursor is display metadata only and does not mark what has been consolidated. Fact/lesson counts and dream timing live here and in the Console, not in memory_stats().
  4. If /health reports degraded (or any component error), surface the failing component verbatim — do not summarize it away. The same goes for a dream_tracking_error field: status stays ok, but the dream cannot pull or commit until it clears, and memory_dream(action="status") carries the detail.
  5. Report the backup from /health's last_backup: its age_hours, and flag it when older than 36 hours (backups have stopped) or when rotation is held (entries, facts or lessons fell sharply, so the backup script kept every older copy — check for a wipe before anyone re-runs it with -AcceptRowDrop). If the key is absent, no backup has been recorded for this daemon: on the Docker tier, suggest ops/backup.ps1 and the daily ops/install-backup-task.ps1.
  6. Mention the Cortex Console for browsing: http://127.0.0.1:8765/ui/
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. 22d ago Changed · +5 lines 6cf794157308
  2. 25d ago Changed · +4 lines 0a45e4d52f23
  3. 1mo ago Changed · +11 lines 038e5cf9fe9a
  4. 1mo ago Changed · +2 lines ce6cd9c929d3
  5. 1mo ago First seen · 25 lines · 14 tokens per session scan A a77ff80ca320

Subscribe to this mod's changes

memory-status is a command published in the GitHub repository Pseudogiant-xr/Pseudolife-MCP (6 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 735 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.