status

status is a command for Claude Code from JubaKitiashvili/context-mem. It costs 20 tokens per session (386 once invoked), scanned A, original, MIT.

A command that reports the current state of context-mem, including stored observations, compressed output, token savings, search features, and the dashboard link.

In plain words
What is it for?
It is for checking observation counts, embeddings, token statistics, journal entries, search methods, and the project dashboard link.
Why use it?
It lets you check whether context-mem has saved useful history and how much conversation space its compression has reduced.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the context-mem plugin — 1 skill, 6 commands, 5 hooks, 1 MCP server shipped together

Good fit It is for checking observation counts, embeddings, token statistics, journal entries, search methods, and the project dashboard link.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/jubakitiashvili/context-mem/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/JubaKitiashvili/context-mem

Made for: Claude Code.

Or install context-mem, the plugin that ships this one along with the rest of its 1 skill, 6 commands, 5 hooks, 1 MCP server.

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 status

README.md
[![agentmods](https://agentmods.dev/badge/commands/jubakitiashvili/context-mem/status.svg)](https://agentmods.dev/commands/jubakitiashvili/context-mem/status)
Your own site
<a href="https://agentmods.dev/commands/jubakitiashvili/context-mem/status"><img src="https://agentmods.dev/badge/commands/jubakitiashvili/context-mem/status.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 386 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00020 $0.00386
Opus 5 $0.00010 $0.00193
Sonnet 5 $0.00004 $0.00077
Haiku 4.5 $0.00002 $0.00039

Measured 8d ago against content hash 9c747b3f2770, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 8d 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 · 41 lines

What it actually says

Show the current context-mem status for this project.

  1. Read .context-mem.json to check configuration (search plugins, lifecycle settings)

  2. Read the database directly for stats:

    node -e "
    const Database = require('better-sqlite3');
    const db = new Database('.context-mem/store.db', { readonly: true });
    const obs = db.prepare('SELECT COUNT(*) as c FROM observations').get();
    const embedded = db.prepare('SELECT COUNT(*) as c FROM observations WHERE embeddings IS NOT NULL').get();
    const stats = db.prepare('SELECT COALESCE(SUM(tokens_in),0) as t_in, COALESCE(SUM(tokens_out),0) as t_out FROM token_stats').get();
    const pct = stats.t_in > 0 ? Math.round(((stats.t_in - stats.t_out) / stats.t_in) * 100) : 0;
    console.log('Observations:', obs.c, '| Embedded:', embedded.c, '| Savings:', pct + '%');
    db.close();
    "
    
  3. Check if activity journal exists and report its size:

    wc -l .context-mem/journal.md 2>/dev/null || echo "No journal yet"
    
  4. Present results in a clean format:

    context-mem status
    ─────────────────
    Observations:  142
    Embedded:      142 (vector search active)
    Token savings: 83%
    Journal:       47 entries
    Search:        bm25 + trigram + levenshtein + vector
    Dashboard:     http://localhost:51893
    
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. 8d ago First seen · 41 lines · 20 tokens per session scan A 9c747b3f2770

Subscribe to this mod's changes

status is a command published in the GitHub repository JubaKitiashvili/context-mem (18 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 386 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.