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 qwerfunch/cladding --skill checkpointgit clone --depth 1 https://github.com/qwerfunch/claddingWrote 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/qwerfunch/cladding/checkpoint)<a href="https://agentmods.dev/skills/qwerfunch/cladding/checkpoint"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/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/qwerfunch/cladding/checkpoint"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/checkpoint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 31 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00090 | $0.00512 |
| Opus 5.5 | $0.00036 | $0.00205 |
| Sonnet 5.5 | $0.00018 | $0.00102 |
| Haiku 4.5 | $0.00009 | $0.00051 |
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 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.
What it actually says
Cladding checkpoint
Run clad checkpoint <featureId> from the project root. Iron Law backbone Phase 1 (iron-law.md §2.5) — the verb only stamps the audit-log entry; it never mutates the working tree or invokes git commit. The maintainer keeps the option to freeze the state with a normal git commit on top.
The checkpoint event payload carries:
featureId— the spec id, accepts bothF-NNNlegacy and six-or-more-hex hash shapes; newly authored records emitF-<hash8>.gitHead— full 40-char commit sha at the time of the call (ornullwhen the project is not a git repository).specDigest— sha-256 over the merged spec for replay verification.timestamp— ISO 8601.
clad checkpoint F-001
clad checkpoint F-a3f9c2e1
The output is a single Pulse line: ✓ checkpoint · <featureId> head=<sha12> digest=<digest12>. The event lands in .cladding/events.log.jsonl as type: "feature_checkpoint" and can be inspected with clad doctor --json or clad_get_events over MCP.
When to use
- Before starting a feature with your AI host so a failed attempt has a known-good target to roll back to.
- Before a manual refactor large enough that
git stashis unwieldy. - Right after
clad syncreports the spec is valid, so the checkpoint pins exactly the validated spec digest the implementation will start from.
Pair with
clad rollback <featureId> — prints the maintainer-runnable git checkout <sha> for the latest checkpoint and stamps a feature_rolled_back event. The pair forms the v0.3.X Iron Law backbone for safe autonomous progress; see skills/rollback/SKILL.md.
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 Changed 1d1d19a04fcf
- 1mo ago First seen · 32 lines · 90 tokens per session scan A f723e8cfb828
checkpoint is a skill published in the GitHub repository qwerfunch/cladding (16 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 512 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-30.
Other skills, from other repositories
investigating-repository-history
Investigate GitHub repository history before risky code changes using git blame/log, GitHub PRs, review comments, squash/rebase/cherry-pick/rename heuristics, and cited evidence. Use when asking why code exists, whether a change is safe, what PR introduced behavior, or before editing API, compatibility, security…
repo-activity-summary
Summarize a repository's recent engineering activity from git history — technologies, work types, churn hotspots, contributor patterns, and velocity. Use when asking "what has this repo been working on", "is this project active", "who contributes what", "where are the hotspots", or before onboarding onto an unfamiliar…
finishing-a-development-branch
Use when development work is complete and you need to prepare for merge. Guides through cleanup, testing, documentation, and creating a well-structured pull request.
git-workflow
Run git status / log / diff and list pull requests for the session's repo via the opendray gateway. Use whenever the user asks about "what's changed", "status", "diff", "open PRs", or wants to commit / push.
worktree-pr
Decide whether a task deserves its own git worktree and, if chosen, run it end to end: branch from the integration branch rather than the current tree, keep the main working copy untouched while the task runs, compare the result against the untouched baseline before declaring it done, and prepare it for a pull request…
review
Structured code review with parallel audit agents, confidence-scored triage, and optional auto-fix. Examines uncommitted changes, staged diffs, commit ranges, or specific paths. Produces a tiered report (MUST-FIX / RECOMMENDED / NIT) backed by evidence, then optionally applies fixes with verification.