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/specnpx skills add toverux/cantrips --skill specgit 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/spec)<a href="https://agentmods.dev/skills/toverux/cantrips/spec"><img src="https://agentmods.dev/badge/skills/toverux/cantrips/spec.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.00016 | $0.00892 |
| Opus 5 | $0.00008 | $0.00446 |
| Sonnet 5 | $0.00003 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
spec 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce a spec from the current conversation and codebase understanding.
Synthesize what you already know — the interview, if any, already happened (/grilling).
Process
-
Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain vocabulary throughout the spec.
-
Read the repo's decision memory: the
AGENTS.mdconventions already in context, plus the records bearing on this feature from whichever knowledge stores the loop config enables — ADRs for decisions already made, solutions for gotchas and approaches that failed before. The loop config translates the storage verbs: it isdocs/agents/cantrips-loop.md, and when that doc is absent the plugin defaults (defaults.md) govern. Fold whatever applies into the spec's decisions. When this feature's decisions conflict with a standing ADR — one whose status isaccepted— flag the conflict explicitly in the spec — name the ADR and the revised decision — and note that the revision routes through/compoundat loop end;/compoundis the ADR store's sole writer, so the standing record stays as written until then. -
Propose the test seams — the places
/implementwill drive TDD (seam vocabulary:/codebase-design). Prefer existing seams to new ones; place any new seam at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.
Check with the user that these seams match their expectations.
- Publish the spec — the publish-spec verb, translated by the loop config from step 2 — using the template below. The published body is frozen: a spec is a point-in-time decision record, and execution state lives in git and the backend, so work-status lines (pending, in-progress, done) never enter the body. Afterthoughts arrive as dated annotations through the annotate-spec verb.
Problem Statement
The problem that the user is facing, from the user's perspective.
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.
- 4d ago First seen · 83 lines · 16 tokens per session scan A 4ddf1c422e27
spec is a skill published in the GitHub repository toverux/cantrips (2 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 892 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 skills, from other repositories
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
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.
review
5-pass structured code review — correctness, security, performance, readability, consistency.
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.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
consult-gov-grant
나에게 맞는 정부·공공기관 지원사업을 찾아주고, 심사 기준에 맞춘 사업계획서·신청서 초안을 만들어 드립니다(Word·한글·Excel 파일까지). 창업자·소상공인·중소기업·연구자·비영리단체·개인 누구나 쓸 수 있습니다. 다음과 같은 요청 시 사용하세요: "정부 지원사업 찾아줘" "우리 상황에 맞는 지원금 있어?" "사업계획서 초안 써줘" "지원서 작성 도와줘" "이 신청서 심사 기준으로 검토해줘" "마감 전에 뭐 준비해야 해?" "예비창업패키지 신청서 만들어줘" "지원금 어떻게 쓰는지 모르겠어" 지원사업 탐색·신청서 작성·서류 검토·일정 관리까지 도와주며, 마지막에…