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/simplifynpx skills add toverux/cantrips --skill simplifygit 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/simplify)<a href="https://agentmods.dev/skills/toverux/cantrips/simplify"><img src="https://agentmods.dev/badge/skills/toverux/cantrips/simplify.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.00032 | $0.01771 |
| Opus 5 | $0.00016 | $0.00886 |
| Sonnet 5 | $0.00006 | $0.00354 |
| Haiku 4.5 | $0.00003 | $0.00177 |
Grade A, and why
simplify 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplify recently changed material while preserving what it does. Prioritize readable, explicit results over compact ones — fewer lines is not the goal.
The contract below governs every step of this pass, and travels verbatim to each fixer dispatched in Step 2.
- Code — same output for every input, same error behavior, same side effects and ordering.
- Agent-facing prose (a skill, an
AGENTS.mdorCLAUDE.md, a rules file — anything an agent loads and acts on) — the instruction set is what is preserved. Cut text that repeats, rambles, or restates what another file already says. Never cut or weaken a sentence that directs an agent to act, forbids an action, gates a step behind a condition, or states how completion is judged — rewording one into a suggestion is weakening it. Where a sentence's kind is uncertain, it stays.
Step 1: Resolve the scope
- If the user named a scope (a file, a directory, "the function I just wrote"), use it as authoritative — do not widen it.
- Otherwise, use the diff between the current branch and its merge-base with the default branch (
git diff <default-branch>...) plus the uncommitted changes (git diff HEAD), which a merge-base diff leaves out. With no base ref, the uncommitted changes alone. Either way, add the files git does not track (git ls-files --others --exclude-standard): a file git does not track appears in no diff, so it joins the scope whole. Snapshot each of those untracked files before Step 3 edits anything — git holds no pre-pass state for them, and Step 4 verifies against pre-pass text. - Outside a git repository, use the files edited earlier in this conversation.
If the scope comes up empty, stop and ask the user what to simplify.
Step 2: Launch three fixers in parallel
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.
- 3d ago First seen · 99 lines · 32 tokens per session scan A 4a6f7b8b13f8
simplify is a skill published in the GitHub repository toverux/cantrips (2 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 1,771 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 skills, from other repositories
agent-identifier
Use when creating or configuring Claude Code agents and their frontmatter.
daily-paper-generator
Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.
apm-usage
Activate when the user asks about APM (Agent Package Manager): installing, configuring, authoring, or troubleshooting AI-agent packages, dependencies, compilation, MCP servers, policy, or any apm CLI command.
review
5-pass structured code review — correctness, security, performance, readability, consistency.
scaffold
Project-aware file generation. Reads existing codebase conventions (naming, structure, imports, exports, test patterns) then generates new files that match exactly. Wires generated files into the project's registration points.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.