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 agentmods add skills/ackeskin/contexture/checkpointnpx skills add AcKeskin/contexture --skill checkpointgit clone --depth 1 https://github.com/AcKeskin/contextureWrote 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/ackeskin/contexture/checkpoint)<a href="https://agentmods.dev/skills/ackeskin/contexture/checkpoint"><img src="https://agentmods.dev/badge/skills/ackeskin/contexture/checkpoint.svg" alt="Measured on agentmods" 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.00066 | $0.02414 |
| Opus 5 | $0.00033 | $0.01207 |
| Sonnet 5 | $0.00013 | $0.00483 |
| Haiku 4.5 | $0.00007 | $0.00241 |
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 2d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
checkpoint
The scope-dialed fit-and-intent organ. One lens — does this serve the original point, cohere with the whole, and what did I learn? — delivered at three zoom levels (one verb, no altitude gaps, batch findings). Delegates orientation, baseline-diff, rendering, routing, and persistence to retrospect-core.
Where it sits. Today's diff reviewers (review rule-drift, pr-review an incoming PR, code-review correctness) judge a change in isolation; the corpus passes audit the whole by governance category. checkpoint is the middle and the lens: it asks fit-and-intent at whatever zoom you're at. Its corpus scope carries the passes absorbed from the retired retrospect + system-review organs — see corpus-passes.md. memory-audit (mechanical integrity) and recap (per-session episodic) stay separate lenses.
When to run
/checkpoint— auto-detect the scope (below) and audit at that zoom./checkpoint --scope diff|module|corpus— force the zoom.- Natural language: "does this change fit the bigger picture", "did I drift from what I wanted", "do these modules I just built actually fit together", "step back on what we shipped".
- Do not auto-fire. Mode A, user-invoked. No hook, no session-end trigger.
1. Resolve scope
Auto-detect from what checkpoint is pointed at; surface the resolved scope in the report header so it's transparent and correctable. --scope always overrides.
| Signal | Scope |
|---|---|
A diff / PR / --since <ref> in play, or a single change unit |
diff |
| A just-built module or named module path(s) — the session's recently-edited subtree(s) | module |
| No specific target / "step back on the project / decisions / organs" | corpus |
| Ambiguous (could be two scopes) | ask once, or honor --scope |
"Just-built" for module scope = the modules touched since the last commit (or this session's Edit/Write targets), grouped by top-level subtree. State which modules it resolved so the user can correct.
What ships with it
1 file 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.
- 2d ago First seen · 92 lines · 66 tokens per session scan A 5dfc733afdef
checkpoint is a skill published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 2,414 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
ocr
AI-powered multi-agent code review. Simulates a team of Principal Engineers reviewing code from different perspectives. Use when asked to review code, check a PR, analyze changes, or perform code review.
generic-fullstack-code-reviewer
Review full-stack code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md compliance. Enforces TypeScript strict mode, input validation, GPU-accelerated animations, and design system consistency. Use when completing features, before commits, or reviewing pull requests.
generic-react-code-reviewer
Review React/TypeScript code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md workflow compliance. Enforces TypeScript strict mode, GPU-accelerated animations, WCAG AA accessibility, bundle size limits, and surgical simplicity. Use when completing features, before commits, or…
generic-static-code-reviewer
Review static site code for bugs, security issues, performance problems, accessibility gaps, and CLAUDE.md compliance. Enforces pure HTML/CSS/JS standards, minimal page weight, mobile-first design. Use when completing features, before commits, or reviewing changes.
OCR Review-to-Approval Loop
Drive a PR to an approved code review by looping OCR's multi-agent review and address steps. Runs /ocr:review then /ocr:address repeatedly until the review verdict is APPROVE, then one final /ocr:address for leftover suggestions, posting every review and every address round to the GitHub PR as comments. Use when the…
code-reviewer
Review code for best practices, bugs, and security issues.