afc:checkpoint

afc:checkpoint is a skill for Claude Code from jhlee0409/all-for-claudecode. It costs 12 tokens per session (630 once invoked), scanned A, original, MIT.

A session checkpoint tool that records the current Git state, active features, task progress, and work context in a file. A checkpoint is a saved snapshot you can use to continue later.

In plain words
What is it for?
Use it before pausing work, switching sessions, or handing a feature to another session for continuation.
Why use it?
It prevents an interrupted coding session from losing track of what was changed or what remains. It keeps only the latest saved state in the checkpoint file.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Part of the afc plugin — 29 skills, 12 agents, 19 hooks shipped together

Good fit Use it before pausing work, switching sessions, or handing a feature to another session for continuation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jhlee0409/all-for-claudecode/checkpoint
Install

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.

Any agent
npx skills add jhlee0409/all-for-claudecode --skill checkpoint
Clone the repo
git clone --depth 1 https://github.com/jhlee0409/all-for-claudecode

Made for: Claude Code.

Or install afc, the plugin that ships this one along with the rest of its 29 skills, 12 agents, 19 hooks.

Wrote 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.

agentmods badge for afc:checkpoint

README.md
[![agentmods](https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/checkpoint/github.svg)](https://agentmods.dev/skills/jhlee0409/all-for-claudecode/checkpoint)
Your own site
<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.

agentmods 80×15 button for afc:checkpoint

Your own site · 80×15
<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>
Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 630 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 526ed066d903, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

skills/checkpoint/SKILL.md · 94 lines

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):

  1. Git status:
    • Current branch
    • Last commit hash + message
    • List of changed files (git status --short)
  2. Active Features:
    • Check subdirectories under .claude/afc/specs/
    • Progress state of each feature (spec only? through plan? implementing?)
  3. Tasks Progress:
    • If tasks.md exists, count [x]/[ ] items
  4. Current Work Context:
    • $ARGUMENTS message
    • 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.

Read the full file on GitHub · 94 lines

Changes

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.

  1. 8d ago First seen · 94 lines · 12 tokens per session scan A 526ed066d903

Subscribe to this mod's changes

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.