Borrowing it
Nothing to install: this file belongs to racecraft-lab/racecraft-plugins-public. 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/racecraft-lab/racecraft-plugins-public/main/.claude/skills/speckit-checkpoint-commit/SKILL.mdgit clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-publicWrote 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/racecraft-lab/racecraft-plugins-public/speckit-checkpoint-commit)<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-checkpoint-commit"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-checkpoint-commit.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.00016 | $0.00544 |
| Opus 5 | $0.00008 | $0.00272 |
| Sonnet 5 | $0.00003 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
speckit-checkpoint-commit 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.
This is a copy
86% identical to speckit-checkpoint-commit — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checkpoint Commit Skill
/speckit.checkpoint.commit
Description
Stages all current changes and creates a commit with a descriptive message reflecting the work just completed. This command should be called by the agent at two points during the spec-kit workflow:
- After each pre-implementation step (constitution, specify, clarify, plan, analyze, tasks) — to capture the spec artifacts produced by that step.
- During implementation — at natural checkpoints, such as after completing a task or a logical group of related tasks from the task list.
When to Commit
Pre-Implementation Steps
Commit immediately after each of these steps completes:
- After constitution — commit the project principles and guidelines
- After specify — commit the requirements and user stories
- After clarify — commit the resolved clarifications
- After plan — commit the technical implementation plan
- After analyze — commit the consistency and coverage analysis
- After tasks — commit the task breakdown
During Implementation
Use the task list generated during the tasks step as a reference for when to commit. Good checkpoints include:
- Completing a single task from the task list
- Completing a logical group of closely related tasks
- Finishing a self-contained unit of work (e.g., a new component, a service layer, a set of tests)
The agent should use judgment — the goal is to produce commits that are meaningful and reviewable, not to commit after every single file change.
Workflow
- Determine a clear, concise commit message based on the work just completed
- Stage all current changes (
git add -A) - Commit with the message (
git commit -m "<message>")
Commit Message Guidelines
- For pre-implementation steps, use the step name as a prefix (e.g.,
constitution: establish project principles,tasks: break down implementation into actionable items) - For implementation commits, describe what was built (e.g.,
implement user authentication service,add product listing page and API routes) - Keep messages concise but descriptive enough to understand the scope of the commit
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 First seen · 63 lines · 16 tokens per session scan A e97ea046292a
speckit-checkpoint-commit is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 544 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to speckit-checkpoint-commit, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
speq-git-discipline
Read-only git guardrails and the Conventional Commits reference — no history writes, verify changes before completing. Triggered by planner-agent, implementer-agent, implementer-expert-agent, and recorder-agent. The headless orchestrators speq-plan-pr and speq-implement-pr are the sole exception: they write git…
gitops
Git operations wrapper: sync, stage, commit, push. Generates Conventional Commits messages with .scratch artifact references. Use when the user says gitops, commit, push, sync code, or needs version control operations.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
gsd-quick-batch
Batch several /gsd:quick-shaped tasks together — planned, dispatched, and merged as one run.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
gsd-pause-work
Create context handoff when pausing work mid-phase.