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/create-checkpointnpx skills add MSiccDev/ai-context-kit --skill create-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.00581 |
| Opus 5 | $0.00022 | $0.00291 |
| Sonnet 5 | $0.00009 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
create-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 yesterday.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Checkpoint
Purpose
Capture the active session state as a structured Markdown checkpoint artifact so the session can be restored in a future conversation.
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/create-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
- When the user signals they are ending the session and want to resume later.
- When the user explicitly requests a checkpoint.
- Do not create checkpoints silently or mid-session without the user's explicit request.
Required Inputs
- Current active values for: project, role, phase, output_style, tone, and interaction_mode (if established).
- Open tasks or confirmed next steps from this session.
- Key decisions made during this session that affect future work.
- File paths actively referenced or modified this session.
Workflow
- Collect the current values for all required schema fields from active session state.
- List all open tasks — items in progress or confirmed next steps.
- List key decisions made this session that would affect future work.
- List file paths actively referenced or modified.
- Draft the checkpoint artifact using the schema in
references/checkpoint-schema.md. - Present the full draft to the user for review and approval before writing anything.
- Write the file only after the user explicitly approves.
- Suggest saving as
checkpoint-YYYY-MM-DD.mdin the project root or acheckpoints/folder if one exists. Let the user decide the exact path.
Output Expectations
- A Markdown file with YAML frontmatter containing all required schema fields.
- Human-readable summary paragraph below the frontmatter is optional but encouraged.
- The file must not be written without explicit user approval.
- Sensitive data (credentials, private client content) must never be included.
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.
- yesterday First seen · 52 lines · 44 tokens per session scan A a75d6096adf4
create-checkpoint is a skill published in the GitHub repository MSiccDev/ai-context-kit (12 stars, last pushed 4d ago), licensed MIT. It adds 44 tokens to every session and 581 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.
validate
Check structure and surface issues for human review. Validates YAML, references, concern coverage, and compilation status.
status
Show what structured context exists and what's missing. Overview of bundles, SCDs, coverage across all 11 concerns, and compilation sync 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.