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/fmflurry/settings-opencode/checkpointgit clone --depth 1 https://github.com/fmflurry/settings-opencodeWhat 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 | $0.00006 | $0.00328 |
| Opus 5 | $0.00003 | $0.00164 |
| Sonnet 5 | $0.00001 | $0.00066 |
| Haiku 4.5 | $0.00001 | $0.00033 |
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 yesterday.
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
95% identical to checkpoint — 2 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.
What it actually says
Checkpoint Command
Save current verification state and create progress checkpoint: $ARGUMENTS
Your Task
Create a snapshot of current progress including:
- Tests status - Which tests pass/fail
- Coverage - Current coverage metrics
- Build status - Build succeeds or errors
- Code changes - Summary of modifications
- Next steps - What remains to be done
Checkpoint Format
Checkpoint: [Timestamp]
Tests
- Total: X
- Passing: Y
- Failing: Z
- Coverage: XX%
Build
- Status: ✅ Passing / ❌ Failing
- Errors: [if any]
Changes Since Last Checkpoint
git diff --stat [last-checkpoint-commit]
Completed Tasks
- Task 1
- Task 2
- Task 3 (in progress)
Blocking Issues
- [Issue description]
Next Steps
- Step 1
- Step 2
Usage with Verification Loop
Checkpoints integrate with the verification loop:
/plan → implement → /checkpoint → /verify → /checkpoint → implement → ...
Use checkpoints to:
- Save state before risky changes
- Track progress through phases
- Enable rollback if needed
- Document verification points
TIP: Create checkpoints at natural breakpoints: after each phase, before major refactoring, after fixing critical bugs.
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.
- yesterday First seen · 68 lines · 6 tokens per session scan A 6e3341520a82
checkpoint is a command published in the GitHub repository fmflurry/settings-opencode (172 stars, last pushed 19d ago), licensed MIT. It adds 6 tokens to every session and 328 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to checkpoint, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.