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 ChenShuo2004/cs-skills --skill cs-checkpoint-versiongit clone --depth 1 https://github.com/ChenShuo2004/cs-skillsWrote 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/chenshuo2004/cs-skills/cs-checkpoint-version)<a href="https://agentmods.dev/skills/chenshuo2004/cs-skills/cs-checkpoint-version"><img src="https://agentmods.dev/badge/skills/chenshuo2004/cs-skills/cs-checkpoint-version/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/chenshuo2004/cs-skills/cs-checkpoint-version"><img src="https://agentmods.dev/badge/skills/chenshuo2004/cs-skills/cs-checkpoint-version.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00083 | $0.01027 |
| Opus 5.5 | $0.00033 | $0.00411 |
| Sonnet 5.5 | $0.00017 | $0.00205 |
| Haiku 4.5 | $0.00008 | $0.00103 |
Grade A, and why
cs-checkpoint-version 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 19d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checkpoint Version
Purpose
Use this skill to create a local, file-based rollback point for one Git repository.
The default goal is safety: preserve the current branch, HEAD, staged diff, unstaged diff, and untracked files without creating a commit or changing the branch.
Rules
- Work in one Git repository root. Confirm with
git rev-parse --show-toplevel. - Create a checkpoint when requested or when this change needs a rollback artifact; do not snapshot every routine edit. Reuse a verified checkpoint only if HEAD, staged/unstaged diffs and untracked inputs have not changed.
- Default to a safe snapshot under
.codex-checkpoints/; do not commit unless the user explicitly asks for a Git checkpoint commit. - Include staged, unstaged, and untracked non-ignored files. Do not include ignored files such as dependencies, builds, caches, or secrets.
- Never restore a checkpoint unless the user explicitly asks to roll back or restore.
- Before restore, preserve the current worktree with a
pre-restorecheckpoint.
Save Workflow
- Inspect the repository:
git rev-parse --show-toplevel
git status --short --branch
-
Pick a short slug from the task, such as
before-refactor,before-release, orcurrent-version. -
Run the bundled script from this skill:
powershell -NoProfile -ExecutionPolicy Bypass -File "<skill-root>\scripts\create-checkpoint.ps1" -Repo "<repo-root>" -Slug "current-version"
- Report:
- checkpoint directory
- branch and HEAD
- whether staged, unstaged, and untracked files were captured
- restore command
Restore Workflow
Use this only after the user explicitly asks to restore a checkpoint.
- Inspect available checkpoints:
Get-ChildItem -Directory "<repo-root>\.codex-checkpoints" | Sort-Object Name -Descending
- Read the checkpoint metadata:
Get-Content "<checkpoint-path>\metadata.json" -Raw
What ships with it
4 files 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.
- 19d ago Changed · -5 lines b4b2832305db
- 1mo ago First seen · 118 lines · 83 tokens per session scan A 8bfb9ad2a779
cs-checkpoint-version is a skill published in the GitHub repository ChenShuo2004/cs-skills (204 stars, last pushed 18d ago), licensed MIT. It adds 83 tokens to every session and 1,027 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.