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 skills add hotalexnet/agent-checkpoint --skill repo-checkpointgit clone --depth 1 https://github.com/hotalexnet/agent-checkpointWrote 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/skills/hotalexnet/agent-checkpoint/repo-checkpoint)<a href="https://agentmods.dev/skills/hotalexnet/agent-checkpoint/repo-checkpoint"><img src="https://agentmods.dev/badge/skills/hotalexnet/agent-checkpoint/repo-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/skills/hotalexnet/agent-checkpoint/repo-checkpoint"><img src="https://agentmods.dev/badge/skills/hotalexnet/agent-checkpoint/repo-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.00068 | $0.00498 |
| Opus 5 | $0.00034 | $0.00249 |
| Sonnet 5 | $0.00014 | $0.00100 |
| Haiku 4.5 | $0.00007 | $0.00050 |
Grade A, and why
repo-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 10d 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
repo Checkpoint
Use this skill inside a git repository.
Why this skill exists
Conversation state is fragile. A repo-local markdown checkpoint is not.
This skill writes a timestamped markdown handoff under the fixed repo-local
directory .agents/checkpoints/ so the next session can recover from any
programming agent: Codex/OpenAI CLI, Claude Code, opencode, or a generic shell
agent. The checkpoint belongs to the repository, not to a particular tool.
- what the user actually wanted
- what constraints mattered
- what files were in play
- what remains next
Mandatory first step
From the target repo root, run:
python3 ~/.agents/skills/repo-checkpoint/scripts/save_checkpoint.py --title "<short-title>" --agent "<codex|claude-code|opencode|other>"
If the skill is vendored into the repo instead of installed globally, run the same script from the vendored path.
Workflow
- Create the scaffold first. Do not invent the path manually.
- Replace every
TODOwith concrete current-session state. - Treat
Agent HandoffandKey Chat Contextas first-class data:- which agent wrote the checkpoint
- which agent should be able to resume it
- where to start without relying on hidden conversation memory
- user goal
- explicit constraints
- scope changes
- rejected paths
- exact wording worth preserving
- Keep
Files In Play,Verification, andNext Stepexecutable. - End with the checkpoint path and tell the user that any supported agent can
run
repo-resumefrom the same repo next time.
Output contract
Keep these top-level sections exactly:
## Agent Handoff## Session Goal## Current State## Key Chat Context## Files In Play## Verification## Next Step## Resume Recipe## Git Snapshot
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 65 lines · 68 tokens per session scan A 31aa3fb65113
repo-checkpoint is a skill published in the GitHub repository hotalexnet/agent-checkpoint (13 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 498 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
ship-it
A GitHub delivery workflow that commits completed changes, pushes a branch, creates and merges a pull request, and closes the related issue.
commit
A commit candidate is the exact patch that will enter the commit. A coherent change has one task or issue as its reason for existing.
writing-git-commits
Write clear, focused Git commit messages and keep commits easy to review.
speq-git-discipline
Read-only git guardrails and the Conventional Commits reference — no history writes, verify changes before completing. Triggered by planner-agent, implementer-agent, implementer-expert-agent, and recorder-agent. The headless orchestrators speq-plan-pr and speq-implement-pr are the sole exception: they write git…
git-github-flow
Use for branch prep, clean commits, PR descriptions, GitHub issue triage, changelogs, release notes, review response, merge readiness, or publishing a branch safely.