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 opsmill/infrahub-mcp --skill speckit-checkpoint-commitgit clone --depth 1 https://github.com/opsmill/infrahub-mcpWrote 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/opsmill/infrahub-mcp/speckit-checkpoint-commit)<a href="https://agentmods.dev/skills/opsmill/infrahub-mcp/speckit-checkpoint-commit"><img src="https://agentmods.dev/badge/skills/opsmill/infrahub-mcp/speckit-checkpoint-commit/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/opsmill/infrahub-mcp/speckit-checkpoint-commit"><img src="https://agentmods.dev/badge/skills/opsmill/infrahub-mcp/speckit-checkpoint-commit.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.00016 | $0.00525 |
| Opus 5.5 | $0.00006 | $0.00210 |
| Sonnet 5.5 | $0.00003 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- speckit-checkpoint-commit — 86% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/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.
- 1mo ago First seen · 58 lines · 16 tokens per session scan A c605eb5845c0
speckit-checkpoint-commit is a skill published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 525 once invoked, about $0.0001 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
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.
commit
Create git commits with good messages. Use when user says "commit", "create commit", or asks to commit changes.
app_tagline_backfill
Give apps built on this instance a share-card tagline when their app.yaml has none. Runs automatically once after Rome upgrades (AUTO mode, list supplied by the caller) or on request from the guardian ("add taglines to my apps", MANUAL mode, confirm before writing). Only touches editable mode: "source" apps — never…
commit
Generate git commit messages from staged changes.
knowledge-shell-process-and-worktree
Shell and Git worktree support for running commands, managing long-lived processes, and giving sessions isolated working directories. A Git worktree is a separate checkout linked to the same repository.
auto-git-commiter
Use when automatically commit and push OpenClaw changes to GitHub. Enable continuous improvement with automatic versioning, changelogs, and deployment-ready commits. Use when working with auto git commiter.