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/codysnider/tagmem/remembergit clone --depth 1 https://github.com/codysnider/tagmemWhat 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.00007 | $0.00151 |
| Opus 5 | $0.00003 | $0.00076 |
| Sonnet 5 | $0.00001 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
remember 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
Save the current conversation into tagmem.
Requirements:
- Write exactly one concise diary entry capturing the highest-signal outcome of this conversation so far.
- Add only the minimum additional durable memory needed: decisions, blockers, preferences, or next steps that are likely to matter later.
- Do not dump the whole conversation into memory.
- Prefer the current project naming convention used for OpenCode sessions as the primary memory topic or tag context.
- If
$ARGUMENTSis present, use it as the topic override. - Keep the saved memory factual, compact, and useful for later retrieval.
If there is not enough substantive content yet, say so briefly instead of forcing low-value memory writes.
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 · 17 lines · 7 tokens per session scan A 5c5e7c0b3be3
remember is a command published in the GitHub repository codysnider/tagmem (15 stars, last pushed 3mo ago), licensed MIT. It adds 7 tokens to every session and 151 once invoked, about $0.0000 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
rp-build-cli
Build with rp-cli context builder → chat → implement.
generate-story
Generate an agentic, fact-grounded relationship story visualization for "$ARGUMENTS".
tree-ring-capture
Capture a concise validated lesson decision warning or preference in Tree Ring Memory.
tree-ring-certify
Generate Tree Ring harness or recall-quality evidence without confusing it with the full framework release suite.
tree-ring-dox-sync
Preview and synchronize DOX-style AGENTS.md guidance as source-linked Tree Ring memory.
tree-ring-recall
Recall durable Tree Ring Memory context before starting or resuming work.