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 pedrohcgs/Claude-Mini --skill checkpointgit clone --depth 1 https://github.com/pedrohcgs/Claude-MiniWrote 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/pedrohcgs/claude-mini/checkpoint)<a href="https://agentmods.dev/skills/pedrohcgs/claude-mini/checkpoint"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-mini/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/pedrohcgs/claude-mini/checkpoint"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-mini/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.00124 | $0.02202 |
| Opus 5.5 | $0.00050 | $0.00881 |
| Sonnet 5.5 | $0.00025 | $0.00440 |
| Haiku 4.5 | $0.00012 | $0.00220 |
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
86% identical to checkpoint — 35 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.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/checkpoint — Structured Session Handoff
Produce a state snapshot that the next session (yours, or a collaborator's, or a fresh-context reboot) can resume from in under a minute. The narrative quality_reports/session_logs/ continues to live separately — /checkpoint writes the structured side: facts, file pointers, and next-actions.
When to use
- Before a long break, model switch (Opus ↔ Sonnet ↔ Haiku), or end of a working day.
- Before auto-compaction would otherwise discard mid-plan context (paired with the PreCompact hook).
- Before handing off to a collaborator on the same repo.
- After completing a chunk of a multi-session plan, when "where am I" is the first question the next session will ask.
When NOT to use
- For the narrative what happened — that lives in
quality_reports/session_logs/(see.claude/rules/session-logging.md). - For commit messages — those go through
/commit, which writes its own structured commit body. - For decisions about alternatives — those go to
templates/decision-record.mdviaquality_reports/decisions/.
The three artifact types are complementary: session-log = narrative, decision-record = trade-off captured, checkpoint = state to resume from.
Workflow
PHASE 1 — Gather state
Read, in this order:
- Most recent plan —
ls -t quality_reports/plans/*.md | head -1. Extract: status (DRAFT / APPROVED / COMPLETED), title, top-level files-to-modify list, and any line that begins with "Open questions" / "Risks" / "Next". - Most recent session log —
ls -t quality_reports/session_logs/*.md | head -1. Extract: latest "Next steps" or "Blockers" lines. - MEMORY.md root — read the table of
[LEARN]entries already on disk so you don't propose duplicates. - Git state —
git log --oneline -20,git status -s,git branch --show-current. Capture: current branch, last 5 subjects, uncommitted file count. - Working files —
git diff --stat HEADto see which files changed in this session (skip if branch is freshly cut; just say "no in-session edits"). - Active TODOs — if a TodoWrite list is in flight in this session, capture the in-progress + next-pending items.
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 · 159 lines · 124 tokens per session scan A b605194b23d3
checkpoint is a skill published in the GitHub repository pedrohcgs/Claude-Mini (11 stars, last pushed 5mo ago), licensed MIT. It adds 124 tokens to every session and 2,202 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to checkpoint, differing in 35 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…