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.
npx agentmods add commands/josephy02/gitmem/memory-reviewgit clone --depth 1 https://github.com/josephy02/gitmemWhat 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 | $0.00010 | $0.00163 |
| Opus 5 | $0.00005 | $0.00081 |
| Sonnet 5 | $0.00002 | $0.00033 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
memory-review 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 yesterday.
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
Review the health of persistent memory:
- Call the
memory_conflictsMCP tool. For each conflict, show both sides with provenance and ask me which is correct (or infer it from the codebase if it's checkable), then resolve by appending acorrectionthat supersedes the losing event ids viamemory_append. - Run
gitmem stalein the shell (if a gitmem root exists). For each possibly-stale fact, check the anchored code and either confirm the fact still holds or append a correction. - Finish with a one-paragraph summary: how many conflicts resolved, how many stale facts confirmed or corrected.
Never delete or edit log files directly — all fixes go through append.
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.
- yesterday First seen · 12 lines · 10 tokens per session scan A baaa8b7f47cc
memory-review is a command published in the GitHub repository josephy02/gitmem (0 stars, last pushed 3d ago), licensed MIT. It adds 10 tokens to every session and 163 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-31.
Other commands, from other repositories
tokenless-stats
Show Tokenless compression statistics.
evolve-lite-subscribe
Add a shared guidelines repo (read-scope subscription or write-scope publish target) to the unified repos list.
cb-search
코드브레인 BM25 검색 — stale 자동 refresh.
graphify
Turn your vault into a clustered knowledge graph with HTML and JSON outputs.
/reddit drives the visible Chrome CDP session for Reddit. It does not use the Reddit API and never launches a headless browser. It acts as whatever Reddit account is logged into the visible session.
scorecard
Run a repeatable weekly health check. Score Brain OS out of 100. Compare week-over-week.