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/plumpslabs/kumaWrote 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/plumpslabs/kuma/kuma-checkpoint)<a href="https://agentmods.dev/commands/plumpslabs/kuma/kuma-checkpoint"><img src="https://agentmods.dev/badge/commands/plumpslabs/kuma/kuma-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/plumpslabs/kuma/kuma-checkpoint"><img src="https://agentmods.dev/badge/commands/plumpslabs/kuma/kuma-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.00014 | $0.00080 |
| Opus 5 | $0.00007 | $0.00040 |
| Sonnet 5 | $0.00003 | $0.00016 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
kuma: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 4d 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.
What it actually says
/kuma:checkpoint
Take an atomic rollback snapshot of current files and knowledge graph.
kuma_safety({ action: "checkpoint", label: "[pre-refactor-feature-x]" })
Creates <label>/ snapshot with kuma.db + modified files.
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.
- 4d ago First seen · 13 lines · 14 tokens per session scan A 3ac34869b5fe
kuma:checkpoint is a command published in the GitHub repository plumpslabs/kuma (2 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 80 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-08.
Other commands, from other repositories
commit-changes-main
Commit directly on main/master when explicitly allowed.
commit-same-branch
Commit on the current branch with conventional message.
commit
Commit on a new branch with conventional message.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.
fest-commit
Commit changes with festival traceability metadata.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.