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/raiyanyahya/recallWrote 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/raiyanyahya/recall/show)<a href="https://agentmods.dev/commands/raiyanyahya/recall/show"><img src="https://agentmods.dev/badge/commands/raiyanyahya/recall/show/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.
<a href="https://agentmods.dev/commands/raiyanyahya/recall/show"><img src="https://agentmods.dev/badge/commands/raiyanyahya/recall/show.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.00062 |
| Opus 5.5 | $0.00005 | $0.00025 |
| Sonnet 5.5 | $0.00002 | $0.00012 |
| Haiku 4.5 | $0.00001 | $0.00006 |
Grade A, and why
show 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 1mo 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
Read .recall/context.md from the project root and display it verbatim.
If it doesn't exist, tell the user no context has been saved yet and suggest
running /recall:save.
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.
- 1mo ago First seen · 10 lines · 12 tokens per session scan A 7fde06c38662
show is a command published in the GitHub repository raiyanyahya/recall (762 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 62 once invoked, about $0.0000 per session on Opus 5.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
ccc-context-budget
Show how full the context window is, which components use the most of it, and when to save the session and compact. Use when the session feels slow, long or near its context limit.
updatespec
Use when a session ends with code or decisions the spec does not reflect yet, or after /ccf:check passes to mark a task done. Refreshes the CCF spec (.claude/rules + CLAUDE.md) AND system memory with what was learned this session, so future sessions start fresh and repeat fewer mistakes. Also records new tools with…
ashlr-compact
Identify stale tool results accumulating in the conversation history and surface a recompression plan.
promote
Show what the tape is holding for your word, and promote the ones you approve into canon. Agent inference never becomes canon on its own — this is the door, and your hand is on it.
bifrost-candidates
Review memory candidates recorded during sessions, and promote the good ones into shared team memory.
pin
Break checkpoint — status display, session log, optional MEMORY.md update.