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/michaelycjo/specseal/checkpointnpx 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.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.1 | $0.00073 | $0.00366 |
| Opus 5 | $0.00036 | $0.00183 |
| Sonnet 5 | $0.00015 | $0.00073 |
| 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 5d 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 (>3 files)
- Deleting files/code
- Migration/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/HIGH]
Affected: [file count] files
Rollback: [git reset --hard HASH / other 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.
- 5d 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 today), licensed MIT. It adds 73 tokens to every session and 366 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…