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/frenzymath/ArchonWrote 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/frenzymath/archon/checkpoint)<a href="https://agentmods.dev/commands/frenzymath/archon/checkpoint"><img src="https://agentmods.dev/badge/commands/frenzymath/archon/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/frenzymath/archon/checkpoint"><img src="https://agentmods.dev/badge/commands/frenzymath/archon/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.00009 | $0.00510 |
| Opus 5.5 | $0.00004 | $0.00204 |
| Sonnet 5.5 | $0.00002 | $0.00102 |
| Haiku 4.5 | $0.00001 | $0.00051 |
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.
What it actually says
Lean4 Checkpoint
Creates a verified checkpoint of your current proof progress.
Usage
/lean4:checkpoint
/lean4:checkpoint "optional custom message"
Inputs
| Arg | Required | Description |
|---|---|---|
| message | No | Custom commit message suffix |
Actions
- Verify Build - Run
lake buildto ensure code compiles (this is a project-wide gate — runs fulllake build, not file-level) - Check Axioms - Verify no unwanted custom axioms:
bash "$LEAN4_SCRIPTS/check_axioms_inline.sh" src/*.lean - Count Sorries - Report current sorry count:
${LEAN4_PYTHON_BIN:-python3} "$LEAN4_SCRIPTS/sorry_analyzer.py" . --format=summary - Stage and Commit - Stage changes and create commit:
git add -A && git status --short git commit -m "checkpoint(lean4): [summary]" - Report Status - Show what was saved
Output
## Checkpoint Created
**Commit:** [hash] - [message]
**Build:** ✓ passing
**Sorries:** [N] remaining
**Axioms:** [status]
**Next steps:**
- Continue with `/lean4:prove`
- Push manually when ready: `git push`
Safety
- Does NOT push to remote (manual only)
- Does NOT create PRs (manual only)
- Does NOT amend commits (each checkpoint = new commit)
- Will NOT create checkpoint if build fails
Rollback
git reset --soft HEAD~1 # Undo last, keep staged
git reset HEAD~1 # Undo last, keep unstaged
git reset HEAD~N # Undo last N commits
Warning: Only use reset before pushing.
See Also
/lean4:prove- Guided cycle-by-cycle proving/lean4:review- Read-only code review/lean4:refactor- Strategy-level proof simplification- Examples
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 · 9 tokens per session scan A 0a6528e34f13
checkpoint is a command published in the GitHub repository frenzymath/Archon (228 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 510 once invoked, about $0.0000 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-30.
Other commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
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.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.