Borrowing it
Nothing to install: this file belongs to senda-labs/DQIII8. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/senda-labs/DQIII8/main/.claude/skills/checkpoint/SKILL.mdgit clone --depth 1 https://github.com/senda-labs/DQIII8Wrote 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/senda-labs/dqiii8/checkpoint)<a href="https://agentmods.dev/skills/senda-labs/dqiii8/checkpoint"><img src="https://agentmods.dev/badge/skills/senda-labs/dqiii8/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/senda-labs/dqiii8/checkpoint"><img src="https://agentmods.dev/badge/skills/senda-labs/dqiii8/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.00029 | $0.00696 |
| Opus 5 | $0.00015 | $0.00348 |
| Sonnet 5 | $0.00006 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade B, and why
checkpoint scanned grade B with 1 finding 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 10d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
tail -20 .claude/checkpoints.log How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/checkpoint — Save and Verify Session State
Save or verify a named checkpoint using git + .claude/checkpoints.log.
Usage
/checkpoint create [name] — Save current state
/checkpoint verify [name] — Compare current state to checkpoint
/checkpoint list — Show recent checkpoints
Create Checkpoint
When create [name] is called:
- Run
/quality-gatequick check (black + pytest -x -q) - Create a git commit with the checkpoint name:
git add -p # stage only intended changes git commit -m "checkpoint: [name]" - Append to
.claude/checkpoints.log(create it first if absent, otherwiseverify/listfail on a fresh install):[ -f .claude/checkpoints.log ] || touch .claude/checkpoints.log echo "$(date +%Y-%m-%d-%H:%M) | [name] | $(git rev-parse --short HEAD)" >> .claude/checkpoints.log - Report:
CHECKPOINT CREATED: [name] @ [hash]
Verify Checkpoint
When verify [name] is called:
- Read the checkpoint hash from
.claude/checkpoints.log[ -f .claude/checkpoints.log ] || touch .claude/checkpoints.log - Compare current state:
git diff [hash]..HEAD --stat git diff [hash]..HEAD -- '*.py' | head -60 - Report:
CHECKPOINT COMPARISON: [name] ============================== Commits since: N Files changed: X added / Y modified / Z deleted Build: PASS / FAIL Tests: +N passed / -N failed
List Checkpoints
[ -f .claude/checkpoints.log ] || touch .claude/checkpoints.log
tail -20 .claude/checkpoints.log
Typical Workflow
/checkpoint create "before-p2a"
→ implement 5 skills + 3 commands
/checkpoint verify "before-p2a"
→ confirm only expected files changed
/checkpoint create "p2a-complete"
Arguments
create [name]: name must be[a-z0-9-_]+, max 40 charsverify [name]: name from log, exact matchlist: no args — shows last 20 entries
Notes
- Checkpoints are git commits — they survive context compaction
- Use before risky multi-file changes (P2, P3 batches)
- If you compact the context afterwards, create the checkpoint first
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.
- 10d ago First seen · 93 lines · 29 tokens per session scan B 640033a34ae7
checkpoint is a skill published in the GitHub repository senda-labs/DQIII8 (11 stars, last pushed 21d ago), licensed MIT. It adds 29 tokens to every session and 696 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
checkpoint-management
Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
merge-queue
Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.