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 MichaelYcJo/SpecSeal --skill checkpointgit clone --depth 1 https://github.com/MichaelYcJo/SpecSealWrote 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/michaelycjo/specseal/checkpoint)<a href="https://agentmods.dev/skills/michaelycjo/specseal/checkpoint"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/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/michaelycjo/specseal/checkpoint"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/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.00073 | $0.00370 |
| Opus 5.5 | $0.00029 | $0.00148 |
| Sonnet 5.5 | $0.00015 | $0.00074 |
| Haiku 4.5 | $0.00007 | $0.00037 |
Grade A, and why
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 7d 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.
What it actually says
checkpoint, state the blast radius before it is too late to ask
Some operations a commit can undo. These are the ones it cannot: what is
deleted, migrated, or renamed across a tree leaves no equivalent to git revert. The point is not the backup: it is naming what would be lost, out
loud, while the user can still say no.
When it applies
- Refactoring more than three files
- Deleting files or code
- Migration or schema changes
- Large-scale renaming
- Changing core abstractions
Steps
-
Assess risk
- What could go wrong?
- Is this reversible?
- What's the blast radius?
-
Create safety net
- Ensure all changes are committed (or stashed)
- Note the current commit hash
- List files that will be affected
-
Confirm with user
- Present: what will change, what could break, rollback plan
- Get explicit approval before proceeding
-
After completion
- Verify nothing unintended changed
- Run tests
- Confirm rollback path still works
Output Format
Risk: [LOW, MEDIUM or HIGH]
Affected: [file count] files
Rollback: [git reset --hard HASH, or another plan]
Proceed? (waiting for user confirmation)
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.
- 7d ago Changed 7618a7998f01
- 2mo ago First seen · 55 lines · 73 tokens per session scan A 0a7de282a64e
checkpoint is a skill published in the GitHub repository MichaelYcJo/SpecSeal (1 stars, last pushed 4d ago), licensed MIT. It adds 73 tokens to every session and 370 once invoked, about $0.0003 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
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
OCR Review-to-Approval Loop
Drive a PR to an approved code review by looping OCR's multi-agent review and address steps. Runs /ocr:review then /ocr:address repeatedly until the review verdict is APPROVE, then one final /ocr:address for leftover suggestions, posting every review and every address round to the GitHub PR as comments with…
deploy-landed
A deployment verification procedure that checks whether the intended code revision is actually running, its environment settings are present, and the product works. A deployment is the process of putting new software on a server or hosting platform.
signing-preflight
Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…