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/msiccdev/ai-context-kit/restore-checkpointnpx skills add MSiccDev/ai-context-kit --skill restore-checkpointgit clone --depth 1 https://github.com/MSiccDev/ai-context-kitWhat 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 | $0.00044 | $0.00553 |
| Opus 5 | $0.00022 | $0.00277 |
| Sonnet 5 | $0.00009 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
restore-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 3d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Restore Checkpoint
Purpose
Load a checkpoint artifact and restore the session state it describes, surfacing any conflicts with active instruction files before any work begins.
How to Invoke
Load or attach this file's contents into your AI session to activate the workflow (paste, upload, or reference with #file:skills/restore-checkpoint/SKILL.md in VS Code Copilot Chat). In Claude Projects, add it to project knowledge. See Invoking Skills in the README for full platform guidance.
When To Use
- At the start of a session when the user provides a checkpoint file.
- Do not apply checkpoint state mid-session or without the user explicitly providing the artifact.
Required Inputs
- The checkpoint artifact file (provided by the user at session start).
- Active instruction files (user context and project AGENTS.md) already loaded in context.
Workflow
- Read the checkpoint artifact and confirm it contains the
checkpoint: truemarker and all required schema fields perreferences/restore-rules.md. - For each field in the checkpoint, compare it against any values defined in active instruction files.
- For each conflict found: surface it explicitly — state the conflicting values from both sources and which source each value comes from.
- Ask the user which source to apply for each conflict.
- Apply instruction file values as the default for any conflict the user does not respond to.
- Present the full resolved session state to the user for confirmation.
- Do not begin any task work until the user has confirmed the restored state.
Output Expectations
- A clear confirmation summary showing all restored session state values and their sources.
- Each conflict recorded as resolved, with the winning source noted.
- Any missing required fields flagged, with the user asked to supply them or apply the instruction file default.
Resources
references/restore-rules.mdfor spec section 4.4.3 restore rules, conflict resolution logic, and examples.
What ships with it
2 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.
- 3d ago First seen · 47 lines · 44 tokens per session scan A e5f09705e88e
restore-checkpoint is a skill published in the GitHub repository MSiccDev/ai-context-kit (12 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 553 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
acontext-installer
Install Acontext, Login & Init Acontext Project, Add Skill Memory to Agent.
add
Process a document (PRD, architecture doc, security requirements, etc.) into structured context. Extracts relevant information and generates appropriate SCDs.
init
Initialize structured context for this project. Scaffolds .scs/ with all 11 concern bundles, scans the project, and recommends where to start.
status
Show what structured context exists and what's missing. Overview of bundles, SCDs, coverage across all 11 concerns, and compilation sync status.
validate
Check structure and surface issues for human review. Validates YAML, references, concern coverage, and compilation status.
use
Add known compliance or regulatory standards (HIPAA, SOC2, PCI, CHAI, GDPR) to your project context. Copies pre-built standards SCDs from the plugin's standards library.