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 commands/sairam0424/mindforge/checkpointgit clone --depth 1 https://github.com/sairam0424/MindForgeWrote 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/commands/sairam0424/mindforge/checkpoint)<a href="https://agentmods.dev/commands/sairam0424/mindforge/checkpoint"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/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.00024 | $0.00593 |
| Opus 5 | $0.00012 | $0.00296 |
| Sonnet 5 | $0.00005 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00059 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MindForge — Checkpoint Command
Usage: /mindforge:checkpoint [create|verify|list|clear] [name]
Lightweight progress markers for a work session. A checkpoint records a name, timestamp, git SHA, and a metrics snapshot (files changed, test pass-rate, coverage, build status), so you can measure forward progress and catch regressions between two points. Distinct from milestones (project lifecycle) — checkpoints are intra-session.
Create Checkpoint
- Run
/mindforge:verify-loop(orverify-phase) to confirm current state is clean. - Capture the marker:
echo "$(date +%Y-%m-%d-%H:%M) | $CHECKPOINT_NAME | $(git rev-parse --short HEAD)" >> .planning/CHECKPOINTS.log
- Snapshot metrics: changed-file count, test pass-rate, coverage %, build status.
- Report checkpoint created.
Verify Checkpoint
- Read the named checkpoint from
.planning/CHECKPOINTS.log. - Compare current state to the checkpoint:
CHECKPOINT COMPARISON: $NAME
============================
Files changed: X
Tests: +Y passed / -Z failed
Coverage: +X% / -Y%
Build: [PASS/FAIL]
- If any metric regressed (tests down, coverage down, build broken), flag it loudly — a checkpoint verify that shows regression is a stop signal.
List Checkpoints
Show all checkpoints with name, timestamp, git SHA, and status (current / behind / ahead relative to HEAD).
Clear
Remove old checkpoints, keeping the last 5.
Workflow
[Start] -> /mindforge:checkpoint create "feature-start"
[Implement] -> /mindforge:checkpoint create "core-done"
[Test] -> /mindforge:checkpoint verify "core-done"
[Refactor] -> /mindforge:checkpoint create "refactor-done"
[PR] -> /mindforge:checkpoint verify "feature-start"
AUDIT linkage
Each create/verify optionally writes a hash-chained AUDIT.jsonl entry:
{ "event": "checkpoint_created", "name": "core-done", "sha": "abc1234", "tests_pass_rate": 1.0, "coverage": 0.0 }
Arguments
$ARGUMENTS:
create <name>— create a named checkpointverify <name>— verify current state against a named checkpointlist— show all checkpointsclear— remove old checkpoints (keeps last 5)
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.
- 3d ago First seen · 77 lines · 24 tokens per session scan A 032f563009e0
checkpoint is a command published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 593 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
factory-merge
Review open PRs thoroughly, fix what's fixable, merge what's good.
autopilot-multi
Multi-story autopilot orchestrator — runs N parallel issue pipelines in isolated git worktrees (v3.6 Phase D thin-slice).
contract-version-bump
Classify and apply a version bump to a machine-readable contract (JSON Schema, API spec, config schema) — version literals, consumer compatibility, changelog entry, downstream drift.
close
End session with verification, commits, and documentation.
factory-work
Dispatch subagents to work agent-ready Linear tickets, land the PRs, report.
commit-all
Stage and commit all current changes with a single message. Auto Git Push will pick up and push to origin within 30s.