Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add atuljha23/holocron/plugin install holocronWrote 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/atuljha23/holocron/recall)<a href="https://agentmods.dev/commands/atuljha23/holocron/recall"><img src="https://agentmods.dev/badge/commands/atuljha23/holocron/recall.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.00026 | $0.00152 |
| Opus 5 | $0.00013 | $0.00076 |
| Sonnet 5 | $0.00005 | $0.00030 |
| Haiku 4.5 | $0.00003 | $0.00015 |
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 6d 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
/holocron:recall
Search for relevant rules captured in past sessions.
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/holocron-cli.js" search $ARGUMENTS
Present the results concisely. If none match, say so; do not hallucinate.
If the user wants to see all recent learnings instead of a search, suggest:
node "${CLAUDE_PLUGIN_ROOT}/scripts/holocron-cli.js" list --limit 20
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.
- 6d ago First seen · 24 lines · 26 tokens per session scan A 48376f90cddc
recall is a command published in the GitHub repository atuljha23/holocron (2 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 152 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
learn
Learn Claude Code best practices and capture lessons into persistent memory.
replay
Automatically find and surface relevant learnings from your pro-workflow database before you start working. Like muscle memory for your coding sessions.
wiki
Build, query, and maintain long-lived knowledge bases. Each wiki = markdown folder + SQLite FTS5 shadow index. Survives sessions, indexes auto-load on SessionStart.
context-optimizer
Diagnose and fix context window problems.
learn-rule
Capture a lesson from this session into permanent memory.
compact-guard
Smart context compaction with state preservation — saves critical state before compact and restores after.