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 skills add benjaminthomas/spec-driven-dev --skill spec-checkpointgit clone --depth 1 https://github.com/benjaminthomas/spec-driven-devWrote 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/benjaminthomas/spec-driven-dev/spec-checkpoint)<a href="https://agentmods.dev/skills/benjaminthomas/spec-driven-dev/spec-checkpoint"><img src="https://agentmods.dev/badge/skills/benjaminthomas/spec-driven-dev/spec-checkpoint/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/benjaminthomas/spec-driven-dev/spec-checkpoint"><img src="https://agentmods.dev/badge/skills/benjaminthomas/spec-driven-dev/spec-checkpoint.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00098 | $0.00896 |
| Opus 5.5 | $0.00039 | $0.00358 |
| Sonnet 5.5 | $0.00020 | $0.00179 |
| Haiku 4.5 | $0.00010 | $0.00090 |
Grade A, and why
spec-checkpoint 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 1mo 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checkpoint Commit
Create a checkpoint commit that captures all current changes — but only after the code passes lint, type check, and build.
Instructions
Step 1: Analyze Changes
Run these commands to understand the full picture:
git status— see all tracked and untracked filesgit diff— see detailed changes in tracked filesgit diff --cached— see already-staged changesgit log -5 --oneline— understand this repo's commit message style
Step 2: Quality Checks
Run all three checks. If any fail, fix the issues before proceeding — do not skip or ignore failures.
npm run lint— fix any lint errorsnpm run type-check— fix any type errors (if the script doesn't exist, trynpx tsc --noEmit)npm run build— fix any build errors
Iterate until all three pass cleanly. Only then move to the next step.
Step 3: Stage Everything
Stage all changes — tracked modifications, deletions, and new untracked files:
git add -A
Then review git status again. If anything staged looks like it could hold secrets —
.env*, *.pem, *_rsa, credentials.json, secrets.*, or an unfamiliar filename that might
contain an API key — unstage it (git restore --staged <file>) and tell the user what was
excluded and why, rather than committing it silently. Don't rely on the filename alone for
anything you don't recognize; skim its diff if you're unsure.
Step 4: Craft the Commit Message
Write a commit message following the project's existing conventions (observed from git log). Structure:
- First line: clear, concise summary in imperative mood (50-72 chars)
- Use conventional commit prefixes where the project uses them:
feat:,fix:,refactor:,docs:,chore:, etc.
- Use conventional commit prefixes where the project uses them:
- Body (separated by blank line): a short TL;DR of the changes — 1-3 sentences max. No bullet lists, no file-by-file breakdowns, no lengthy explanations.
- Footer: co-author attribution, naming whichever agent/model is actually running this skill — never hardcode a specific vendor or model name, since this skill runs under many different hosts
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.
- 1mo ago First seen · 95 lines · 98 tokens per session scan A 1c1ea2858bb2
spec-checkpoint is a skill published in the GitHub repository benjaminthomas/spec-driven-dev (1 stars, last pushed 2mo ago), licensed MIT. It adds 98 tokens to every session and 896 once invoked, about $0.0004 per session on Opus 5.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-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
git-workflow
Trunk-based development with atomic commits, clean history, and meaningful commit messages. Every commit should be deployable.
to-code
Phase 3 of the Pólya Heuristic Coder: Carrying Out the Plan, Clean Architecture Seams, Two-Layer Testing Mandate, Inductive Verification, Floor-Guard Anti-Cheat, and Atomic Conventional Commits.
to-stack
Split a large branch or PR into a stack of small PRs, verified layer by layer, and open them as linked drafts.
polya-code
Phase 3 of the Pólya Heuristic Coder: Carrying Out the Plan, Clean Architecture Seams, Two-Layer Testing Mandate, Inductive Verification, Floor-Guard Anti-Cheat, and Atomic Conventional Commits.
commit
Group unstaged changes into atomic commits by concern, matching repository style. Use when asked to "commit", "create a commit", or "commit changes". Don't use for pushing or pull requests (/to-pr).