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.
git clone --depth 1 https://github.com/JubaKitiashvili/context-memWrote 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.
[](https://agentmods.dev/commands/jubakitiashvili/context-mem/status)<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>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.
| Model | Per session | Once 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 |
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.
What it actually says
Show the current context-mem status for this project.
-
Read
.context-mem.jsonto check configuration (search plugins, lifecycle settings) -
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(); " -
Check if activity journal exists and report its size:
wc -l .context-mem/journal.md 2>/dev/null || echo "No journal yet" -
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
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.
- 8d ago First seen · 41 lines · 20 tokens per session scan A 9c747b3f2770
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.
Other commands, from other repositories
memory-why
Show why a memory recall returned what it did -- BM25 vs vector vs hybrid provenance.
context-stats
Display context window usage and token statistics.
handoff
Create a handoff document for seamless session continuity.
capturar
Capturar ideas y notas sin interrumpir el flujo de trabajo. Usa cuando el usuario dice "capturar idea", "quick note", "nota rápida", "grab this", "take a note", "guardar idea", "note to self", "capture thought", "I should remember", "guardar esto". Guarda en memoria persistente sin romper el contexto actual.
check
Run mneme check against a file or proposed change.
context
Retrieve relevant decisions from project memory for the current task.