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 jmagly/aiwg --skill checkpointgit clone --depth 1 https://github.com/jmagly/aiwgWrote 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/jmagly/aiwg/checkpoint)<a href="https://agentmods.dev/skills/jmagly/aiwg/checkpoint"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/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/jmagly/aiwg/checkpoint"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/checkpoint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 146 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00021 | $0.01371 |
| Opus 5.5 | $0.00008 | $0.00548 |
| Sonnet 5.5 | $0.00004 | $0.00274 |
| Haiku 4.5 | $0.00002 | $0.00137 |
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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checkpoint
You create, list, or recover lightweight mid-workflow checkpoints that allow a crashed or interrupted workflow to continue from a known-good position rather than restart from scratch.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "save my place" → create checkpoint at current position
- "mark progress" → create checkpoint
- "pick up where we left off" → recover from most recent checkpoint
- "what checkpoints exist" → list checkpoints
- "resume from checkpoint" → recover from specified or latest checkpoint
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Create (named) | "checkpoint this as iteration-3-complete" | Run aiwg checkpoint create --name iteration-3-complete |
| Create (anonymous) | "create a checkpoint" | Run aiwg checkpoint create |
| List | "show available checkpoints" | Run aiwg checkpoint list |
| Recover (latest) | "recover from the last checkpoint" | Run aiwg checkpoint recover |
| Recover (specific) | "recover checkpoint ckpt_7b2f1a" | Run aiwg checkpoint recover ckpt_7b2f1a |
Behavior
When triggered:
-
Extract intent:
- Which subcommand:
create,list, orrecover? - Is a name or checkpoint ID provided?
- For recover, should it use the most recent checkpoint or a specific one?
- Which subcommand:
-
Run the appropriate subcommand:
# Create — anonymous aiwg checkpoint create # Create — named aiwg checkpoint create --name <name> # List all checkpoints aiwg checkpoint list # Recover — most recent checkpoint aiwg checkpoint recover # Recover — specific checkpoint by ID or name aiwg checkpoint recover <id> -
Checkpoints vs. snapshots: Checkpoints are lightweight — they record the current workflow phase and step plus any in-progress artifact paths, not full artifact checksums. Use snapshots for complete point-in-time captures; use checkpoints for crash recovery during active workflows.
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 · 147 lines · 21 tokens per session scan A fb19ac0212b2
checkpoint is a skill published in the GitHub repository jmagly/aiwg (225 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 1,371 once invoked, about $0.0001 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-03.
Other skills, from other repositories
rally
Orchestrating multi-session parallel execution via Claude Code Agent Teams API and Codex CLI Subagents — launch, manage, coordinate concurrent tasks. Use when parallel work is needed.
void
Verifying YAGNI, cutting scope, and proposing complexity reductions. A 'subtraction' agent questioning the justification for every feature, dependency, doc, and config. Does not write code.
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) development methodology with multi-agent orchestration. Use when running a structured spec-to-code workflow or decomposing a feature through the SPARC phases.
hive-mind-advanced
Queen-led collective-intelligence coordination with consensus mechanisms and persistent shared memory. Use when orchestrating a large swarm of agents under a lead coordinator, building consensus across agents, or maintaining durable cross-agent memory.
stream-chain
Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows. Use when piping output between agents/tools as streaming JSON or building a sequential transform pipeline.
cron-scheduler
Schedules recurring or delayed agent tasks. Use for: schedule this, run daily, cron job, set timer.