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/toverux/cantrips/compoundnpx skills add toverux/cantrips --skill compoundgit clone --depth 1 https://github.com/toverux/cantripsWrote 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/toverux/cantrips/compound)<a href="https://agentmods.dev/skills/toverux/cantrips/compound"><img src="https://agentmods.dev/badge/skills/toverux/cantrips/compound.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.00074 | $0.01059 |
| Opus 5 | $0.00037 | $0.00530 |
| Sonnet 5 | $0.00015 | $0.00212 |
| Haiku 4.5 | $0.00007 | $0.00106 |
Grade A, and why
compound 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 4d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harvest what this session learned so future sessions inherit it. Only knowledge that compounds gets written; every write is approved by the user first.
1. Scan the session
Sweep the whole session for candidates: corrections the user made and preferences they stated, conventions that emerged, durable decisions settled or reversed, gotchas and root causes uncovered, approaches that failed and why, domain terms coined or clarified ("we call this X, not Y"), and workflow friction a procedure could remove.
2. Apply the quality bar
For each candidate, two questions: would this change a future agent's behavior in a different session, and is it non-obvious and stable? Any "no" → discard.
This bar is the defence against the eager-auto-memory failure mode: session-specific trivia — in-flight task state, one-off values, things any agent would infer anyway — must die here.
If nothing clears the bar, say so in one line and stop.
3. Route each survivor
- Project
AGENTS.md— durable shared preferences and conventions, cheap enough to always load. Domain terms go in its glossary section; when the glossary outgrowsAGENTS.md, propose graduating it to aCONCEPTS.mdfile. docs/adr/(opt-in store) — durable decisions: a project-shaping choice settled among live alternatives — whereAGENTS.mdholds preferences anddocs/solutions/holds problem-shaped learnings. One record per decision, peradr-format.md. Reversing a standing decision routes as a pair — a new ADR plus the status flip on the superseded record.docs/solutions/(opt-in store) — problem-shaped learnings: root cause, gotcha, what didn't work. One small file per solved problem, persolutions-format.md. Expensive knowledge, loaded on demand.- Project-local rules — path-scoped project conventions, when the project uses rules files.
- Skills — project-specific procedures → the project's skills directory (
.claude/skills/on Claude Code, or the harness's equivalent); generic workflow improvements → the user's personal skills collection, if configured. - User-global memory file (
~/.claude/CLAUDE.mdon Claude Code,~/.codex/AGENTS.mdon Codex CLI, or the harness's equivalent) — personal-only preferences, and the staging area to trial a candidate durable preference before graduating it to a shared file.
What ships with it
3 files 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.
- 4d ago First seen · 55 lines · 74 tokens per session scan A 9c7e1f60e953
compound is a skill published in the GitHub repository toverux/cantrips (2 stars, last pushed 5d ago), licensed MIT. It adds 74 tokens to every session and 1,059 once invoked, about $0.0004 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
qmd
Search the vault using QMD semantic search. Use PROACTIVELY before reading files. Preference order: (1) MCP tools — mcpqmdquery, mcpqmdget, mcpqmdmultiget, mcpqmdstatus — if they appear in your tool menu, use them first; (2) CLI qmd --index ... as fallback; (3) Grep/Glob only when QMD is not installed. Trigger…
sessions
Search and ask questions about coding agent session history across Claude Code, Codex, and Cursor. Use when asking what was worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior…
handover
Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".
map-debug
Structured MAP debugging via task-decomposer, actor, and monitor agents. Use when reproducing a bug, isolating a regression, or diagnosing an error with specialized agents — including failing or flaky tests (pytest AssertionError), crashes and segmentation faults, memory-corruption or memory errors in native/C…
map-memory-now
Finalize cross-session memory on demand; --finalize-all sweeps every dirty scratch. Use when ending a long session or before switching branches. Do NOT use for routine edits — finalize auto-runs at next SessionStart. Requires claude + git.
compact-kb
Use only when user explicitly invokes $compact-kb.