Borrowing it
Nothing to install: this file belongs to WILLOSCAR/research-units-pipeline-skills. 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/WILLOSCAR/research-units-pipeline-skills/main/.codex/skills/checkpoint-brief/SKILL.mdgit clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-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/willoscar/research-units-pipeline-skills/checkpoint-brief)<a href="https://agentmods.dev/skills/willoscar/research-units-pipeline-skills/checkpoint-brief"><img src="https://agentmods.dev/badge/skills/willoscar/research-units-pipeline-skills/checkpoint-brief/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/willoscar/research-units-pipeline-skills/checkpoint-brief"><img src="https://agentmods.dev/badge/skills/willoscar/research-units-pipeline-skills/checkpoint-brief.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.00035 | $0.00354 |
| Opus 5 | $0.00017 | $0.00177 |
| Sonnet 5 | $0.00007 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
checkpoint-brief 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 12d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 12d ago First seen · 51 lines · 35 tokens per session scan A 2e0a6d2d7dd9
checkpoint-brief is a skill published in the GitHub repository WILLOSCAR/research-units-pipeline-skills (506 stars, last pushed today), with no licence file. It adds 35 tokens to every session and 354 once invoked, about $0.0002 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-30.
Other skills, from other repositories
swarm-manager-review
Produce verification evidence so a human can decide whether to archive (accept) or follow up on a completed backlog item. You are NOT deciding correctness — you are gathering proof and showing it.
utils-unification
Prioritize extracting, standardizing, and consolidating utilities so shared logic is consistent, discoverable, and testable. The goal is to prevent duplication and drift while keeping utilities sharply scoped and aligned to screaming architecture.
refactor
Prioritize code quality, structure, and maintainability across this scenario’s implementation. Do not change the intended behavior, regress tests, or weaken safety guarantees; all changes must maintain or improve completeness.
scenario-readiness-review
Assess whether a scenario's uncommitted changes are ready to commit by querying the git-control-tower unified review endpoint for code health signals, then reviewing the actual git changes for coherence and intent.
screaming-architecture-audit
Prioritize improving the internal architecture and structure of this scenario.
boundary-of-responsibility-enforcement
Prioritize ensuring that each part of the scenario is only doing the work it is responsible for.