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/atuljha23/holocron/learngit clone --depth 1 https://github.com/atuljha23/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/learn)<a href="https://agentmods.dev/commands/atuljha23/holocron/learn"><img src="https://agentmods.dev/badge/commands/atuljha23/holocron/learn.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 | $0.00031 | $0.00408 |
| Opus 5 | $0.00015 | $0.00204 |
| Sonnet 5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
learn 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
/holocron:learn
Capture a rule that Claude should honor in future sessions.
If $ARGUMENTS is already a full invocation
Pass it through to the CLI:
node "${CLAUDE_PLUGIN_ROOT}/scripts/holocron-cli.js" add $ARGUMENTS
Otherwise, extract fields
If the user gave prose, extract:
- title (short — 5–10 words — what this learning is about)
- rule (the imperative — "always do X" / "never do Y")
- reason (the "why" — usually ties to an incident, preference, or architectural constraint)
- tags (comma-separated — e.g.
testing,db,frontend,a11y,security) - scope (
userby default — follows you across projects;project— lives in this repo's.holocron/)
Then run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/holocron-cli.js" add \
--title "<title>" \
--rule "<rule>" \
--reason "<reason>" \
--tags "<tags>" \
--scope <scope>
Rules for what to save
Save when the correction is durable — a rule that should apply to future work. Do NOT save:
- One-off debugging details
- Current-task scratch state
- Things the code already enforces
See also: /holocron:recall <query> to search, /holocron:list to browse.
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 · 49 lines · 0 tokens per session scan A 68e1b827b49c
learn is a command published in the GitHub repository atuljha23/holocron (2 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 408 once invoked, about $0.0002 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.
insights
Surface patterns from your pro-workflow learnings and session history.
wiki
Build, query, and maintain long-lived knowledge bases. Each wiki = markdown folder + SQLite FTS5 shadow index. Survives sessions, indexes auto-load on SessionStart.
handoff
Generate a structured handoff document that another Claude session (or your future self) can consume immediately to continue where you left off.
commit
Create a well-crafted commit after running pro-workflow quality checks.
skill-optimize
Train a skill's SKILL.md by running a SkillOpt-flavored offline loop over accumulated learn-rule corrections.