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 skills/andresanemic/lore-plugin/save-to-lorenpx skills add andresanemic/lore-plugin --skill save-to-loregit clone --depth 1 https://github.com/andresanemic/lore-pluginWrote 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/skills/andresanemic/lore-plugin/save-to-lore)<a href="https://agentmods.dev/skills/andresanemic/lore-plugin/save-to-lore"><img src="https://agentmods.dev/badge/skills/andresanemic/lore-plugin/save-to-lore.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.00148 | $0.08368 |
| Opus 5 | $0.00074 | $0.04184 |
| Sonnet 5 | $0.00030 | $0.01674 |
| Haiku 4.5 | $0.00015 | $0.00837 |
Grade A, and why
save-to-lore 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 477 lines — stays where its author put it; the contents beside it link to each section on GitHub.
save-to-lore — Incremental capture and promotion
The bug is fixed. The tests pass. You are already reaching for the next thing — and the most expensive part of the last two hours is not the patch, it is the sentence you would say if someone asked why it had to be done that way. That sentence has about a minute left before it is gone.
This skill catches it. It captures a friction into the current project's lore/, then promotes
to the project's mother area the clues that are already confirmed + generic. It is the
incremental counterpart to the structural skills: transmute-lore migrates a whole project;
save-to-lore adds one clue at a time and routes it to the right level.
This pass is bracketed by MYCELIUM, and both ends are mandatory. Set up two todos before you write anything. Entry: if this pass will lean on existing Lore to decide where things go, open with a MYCELIUM entry scan (
transmute-loreMYCELIUM) and address its findings first. Exit: after you write, close with a MYCELIUM exit scan over what this pass produced — detail in Closing either mode, below. The pass is not complete — do not report success, do not hand back control — until the exit scan has run and every finding is written as a junction or explicitly declined with a reason. Deferring a junction "to a later pass" is not a completion state; it is the exact failure the exit scan exists to catch.
Language rule: write every clue, index line and law in the language the target lore already uses (consistency wins); if the lore has no established language yet, use the user's language — never English by default. The same applies to filenames: new module files are named in the target lore's language, and existing files are never renamed by this skill (that is
transmute-loreTRANSLATE's job). Artifact names in this skill (identidad.md,principios.md,proyecto.md…) are Spanish canonical forms — use the corpus's actual localized names. Relative paths, confidence markers (conjecture/confirmed), the· ↑glyph, the<!-- lore:always-on -->marker pair and general technical English terms stay as-is.
The area is the shared corpus. A project lives in
{area}/proyectos/{name}/and inherits from{area}/lore/. Generic, confirmed criteria belongs in the area (every project sees it); project-specific criteria stays in the project. This skill decides which is which.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 477 lines · 148 tokens per session scan A 177dc6d08b2b
save-to-lore is a skill published in the GitHub repository andresanemic/lore-plugin (6 stars, last pushed 3d ago), licensed MIT. It adds 148 tokens to every session and 8,368 once invoked, about $0.0007 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 skills, from other repositories
remember
Capture a durable learning into the personal Trove. Use when the user says remember this, note this, save to trove, add to my trove, or when a session surfaces a decision, gotcha, convention/preference, or external reference worth keeping. Writes one atomic entry file and updates INDEX.md.
init
Initialize a personal Trove, a local file-based knowledge index for Claude Code. Use when the user says start/set up/create my trove, or when they want to remember things but no trove exists yet. Scaffolds the trove directory, INDEX.md and entries/ folder at user scope (/.claude/trove, follows you everywhere) or…
index
Index the repository into Trove memory layers (symbols, modules, subsystems, architecture). Use when the user asks to index the repo, build the trove index, refresh symbols, or re-index after large changes.
query
Progressive retrieval from the Trove index. Use when the user asks what Trove knows about a subsystem, where code lives, or wants context assembled before editing. Runs architecture -> subsystem -> module -> symbol retrieval with a context budget.
context-ingest
The single entry point for getting anything new into your context architecture. Takes any input (documents, URLs, YouTube, meeting notes, pasted content) and triages it: dump to inbox, park in planned, or integrate into active docs. WHEN TO USE: "Here's a document — integrate it into my context" "Save this for later"…
context-audit
Audits context architecture for CLEAR compliance, boundary enforcement, and consistency. WHEN TO USE: User says "audit context for CLEAR" User asks "check for duplication across data points" User requests "find boundary violations in [area]" Planning restructuring work Before adding new data points (cleanup existing…