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.
git clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/checkpoint)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/checkpoint"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/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/commands/sifxprime/kodelyth-ecc/checkpoint"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/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.00010 | $0.00419 |
| Opus 5.5 | $0.00004 | $0.00168 |
| Sonnet 5.5 | $0.00002 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
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 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.
This is a copy
94% identical to checkpoint — 5 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
Create or verify a checkpoint in your workflow.
Usage
/checkpoint [create|verify|list] [name]
Create Checkpoint
When creating a checkpoint:
- Run
/verify quickto ensure current state is clean - Create a git stash or commit with checkpoint name
- Log checkpoint to
.claude/checkpoints.log:
echo "$(date +%Y-%m-%d-%H:%M) | $CHECKPOINT_NAME | $(git rev-parse --short HEAD)" >> .claude/checkpoints.log
- Report checkpoint created
Verify Checkpoint
When verifying against a checkpoint:
-
Read checkpoint from log
-
Compare current state to checkpoint:
- Files added since checkpoint
- Files modified since checkpoint
- Test pass rate now vs then
- Coverage now vs then
-
Report:
CHECKPOINT COMPARISON: $NAME
============================
Files changed: X
Tests: +Y passed / -Z failed
Coverage: +X% / -Y%
Build: [PASS/FAIL]
List Checkpoints
Show all checkpoints with:
- Name
- Timestamp
- Git SHA
- Status (current, behind, ahead)
Workflow
Typical checkpoint flow:
[Start] --> /checkpoint create "feature-start"
|
[Implement] --> /checkpoint create "core-done"
|
[Test] --> /checkpoint verify "core-done"
|
[Refactor] --> /checkpoint create "refactor-done"
|
[PR] --> /checkpoint verify "feature-start"
Arguments
$ARGUMENTS:
create <name>- Create named checkpointverify <name>- Verify against 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.
- 1mo ago First seen · 80 lines · 10 tokens per session scan A 00cee3320ba7
checkpoint is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 12d ago), licensed MIT. It adds 10 tokens to every session and 419 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to checkpoint, differing in 5 lines, and is treated as a copy.
Other commands, from other repositories
build
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.
build
A command for carrying out the next unfinished coding task from a plan, including writing tests, implementing the change, checking the project, and committing it. TDD, or test-driven development, means writing a failing test before the code that makes it pass.
handoff
Emit a handoff artifact for this session (optionally specify a slug).
icode
An end-to-end coding workflow invoked with the /icode command and several task-specific options. It routes work through steps such as planning, coding, review, verification, documentation, and worktree management.
kuma:checkpoint
📸 Kuma Checkpoint — Create an atomic named snapshot before risky work.