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/absolutemode/session-recall/recallgit clone --depth 1 https://github.com/AbsoluteMode/session-recallWhat 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.00021 | $0.00182 |
| Opus 5 | $0.00010 | $0.00091 |
| Sonnet 5 | $0.00004 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
recall 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 3d 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
Recall the topic: "$ARGUMENTS" from the unified Claude Code + Codex + Cursor session index.
If the host exposes the dedicated recall subagent, dispatch it (in Claude Code:
subagent_type: session-recall:recall). Otherwise search iteratively with recent_sessions,
recall_search, expand_around/step, and grep.
Use a requested claude, codex, or cursor source filter; otherwise search all three. Return only a tight brief:
task, key decisions and why, tried/rejected approaches, current state, and
source + session_id + uuid pointers.
If "$ARGUMENTS" is empty, ask the user what to recall.
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.
- 3d ago First seen · 16 lines · 21 tokens per session scan A faccebc571d9
recall is a command published in the GitHub repository AbsoluteMode/session-recall (12 stars, last pushed 26d ago), licensed MIT. It adds 21 tokens to every session and 182 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
refactor-function
Automated function complexity reduction using multi-agent workflow.
rp-build-cli
Build with rp-cli context builder → chat → implement.
rp-reminder-cli
Continue your current workflow using rp-cli instead of built-in alternatives.
index
Index the codebase for semantic search.
index
Visual overview of Beacon index — chunks, coverage, provider. Pass --files to list indexed files.
codesage-reindex
Force an incremental codesage re-index (use when git hooks didn't fire). Auto-cleans orphan vec tables if the config model has changed.