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 jhlee0409/all-for-claudecode --skill checkpointgit clone --depth 1 https://github.com/jhlee0409/all-for-claudecodeWrote 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/jhlee0409/all-for-claudecode/checkpoint)<a href="https://agentmods.dev/skills/jhlee0409/all-for-claudecode/checkpoint"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/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/jhlee0409/all-for-claudecode/checkpoint"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/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.00012 | $0.00630 |
| Opus 5 | $0.00006 | $0.00315 |
| Sonnet 5 | $0.00002 | $0.00126 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
afc: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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/afc:checkpoint — Save Session State
Saves the current work state to .claude/afc/memory/checkpoint.md. Preserves progress even if the session is interrupted.
Arguments
$ARGUMENTS— (optional) checkpoint message (e.g., "Phase 2 complete, before starting UI implementation")
Current State (auto-loaded)
!git rev-parse --abbrev-ref HEAD 2>/dev/null || echo "[NO_BRANCH]"
!git log --oneline -1 2>/dev/null || echo "[NO_COMMITS]"
!ls .claude/afc/specs/ 2>/dev/null || echo "[NO_SPECS]"
Execution Steps
1. Collect Current State
Collect automatically (use pre-fetched state above when available):
- Git status:
- Current branch
- Last commit hash + message
- List of changed files (
git status --short)
- Active Features:
- Check subdirectories under
.claude/afc/specs/ - Progress state of each feature (spec only? through plan? implementing?)
- Check subdirectories under
- Tasks Progress:
- If tasks.md exists, count
[x]/[ ]items
- If tasks.md exists, count
- Current Work Context:
$ARGUMENTSmessage- Recently modified files (
git diff --name-only)
2. Save Checkpoint
Overwrite .claude/afc/memory/checkpoint.md (keep only the latest state):
# Session Checkpoint
> Saved: {YYYY-MM-DD HH:mm}
> Branch: {branch name}
> Commit: {hash} — {message}
## Message
{$ARGUMENTS or "automatic checkpoint"}
## Active Features
| Feature | Status | Progress |
|---------|--------|----------|
| {name} | {spec/plan/implementing/done} | {N/M tasks} |
## Incomplete Work
{concrete next steps}
## Changed Files
```
{git status --short output}
```
## Context Notes
{things to remember about the current work}
3. Final Output
Checkpoint saved
├─ Time: {HH:mm}
├─ Branch: {branch name}
├─ Active features: {count}
├─ Progress: {completed tasks}/{total tasks}
└─ Restore: /afc:resume
Notes
- Overwrite: Always keep only the latest state. Git handles history.
- Auto-collect: Collect information automatically as much as possible. Minimize user input.
- Keep it concise: Exclude unnecessary details. Only what is needed to restore.
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.
- 8d ago First seen · 94 lines · 12 tokens per session scan A 526ed066d903
afc:checkpoint is a skill published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 630 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-08-31.
Other skills, from other repositories
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
self-assessment
Interactive skill assessment with personalized learning path generation.
orchestrator-lanes
A file-based project-management playbook for a specific Claude Code development orchestrator. It organizes work into lanes, plans, dependency steps, validation phases, and shipping stages.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.
investigate
Systematic root-cause debugging: find the cause before writing any fix.