Borrowing it
Nothing to install: this file belongs to myICOR/myPKA. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/myICOR/myPKA/main/.claude/skills/checkpoint/SKILL.mdgit clone --depth 1 https://github.com/myICOR/myPKAWrote 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/myicor/mypka/checkpoint)<a href="https://agentmods.dev/skills/myicor/mypka/checkpoint"><img src="https://agentmods.dev/badge/skills/myicor/mypka/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/myicor/mypka/checkpoint"><img src="https://agentmods.dev/badge/skills/myicor/mypka/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.00092 | $0.00448 |
| Opus 5.5 | $0.00037 | $0.00179 |
| Sonnet 5.5 | $0.00018 | $0.00090 |
| Haiku 4.5 | $0.00009 | $0.00045 |
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
You are Larry.
Run this only when the user asks for it by name.
Read 06 AI Team/AI Team Knowledge/Workstreams/WS-1005-checkpoint.md now and follow it exactly. That file is the procedure; this file is the door.
Run python3 "06 AI Team/AI Team Knowledge/Scripts/checkpoint.py" --json with your shell tool, from the folder that holds AGENTS.md, before step 1, unless its output is already below. Read that output; do not run it twice.
!python3 "${CLAUDE_PROJECT_DIR}/06 AI Team/AI Team Knowledge/Scripts/checkpoint.py" --json
Script calls the procedure names, by path:
06 AI Team/AI Team Knowledge/Scripts/checkpoint.py06 AI Team/AI Team Knowledge/Scripts/new-task.py06 AI Team/AI Team Knowledge/Scripts/resolve.py06 AI Team/AI Team Knowledge/Scripts/new-session-log.py
Resources (open only when a step names them):
06 AI Team/Agents/Larry/AGENT.md06 AI Team/AI Team Knowledge/Workstreams/WS-1005-checkpoint.md
Return the completion evidence the procedure's last step names, and nothing it does not.
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 · 32 lines · 92 tokens per session scan A eb5724879a7a
checkpoint is a skill published in the GitHub repository myICOR/myPKA (318 stars, last pushed 22d ago), licensed MIT. It adds 92 tokens to every session and 448 once invoked, about $0.0004 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-09-26.
Other skills, from other repositories
lov-rename-project
A project-renaming workflow that updates a product or repository name across source files, configuration, and documentation. It produces a reviewable plan and preserves compatibility-sensitive names and references where needed.
lov-repo2docs
Turn any folder of source material — a code repository, a pile of articles, a mixed knowledge dump with images — into a professional, polished Fumadocs (Next.js) documentation website, then deploy it to https://{product-id}.example.com/docs. Works by reading the folder one unit at a time and incrementally growing and…
lov-atom-feature-dev
An end-to-end workflow for building a small, self-contained feature across its shared core, command-line tool, API, user interface, saved parameter presets, agent tool, and debugging panel. It uses one contract and shared test cases across the pieces.
lov-plane-cli
A command-line assistant for reading and writing Plane, a project-management system for projects, work items, cycles, modules, statuses, and labels. It connects to a self-hosted or cloud Plane instance through its API.
lov-gh-tidy
Interactive GitHub repo hygiene skill. Lists all open issues, PRs, stale branches, and orphan labels, shows a summary of each with analysis, then asks the user how to handle each item (close, merge, comment, delete, keep). Executes all chosen actions via gh CLI. Use when the user says "清理 GitHub", "tidy repo", "clean…
lov-read-codex-session
A read-only tool for inspecting a local Codex task or conversation, including recent progress, tool activity, status, and results. Codex is a coding-agent environment where work is recorded in task threads.