Borrowing it
Nothing to install: this file belongs to desek/outlook-local-mcp. 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/desek/outlook-local-mcp/main/.agents/skills/checkpoint-read/SKILL.mdgit clone --depth 1 https://github.com/desek/outlook-local-mcpWrote 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/desek/outlook-local-mcp/checkpoint-read)<a href="https://agentmods.dev/skills/desek/outlook-local-mcp/checkpoint-read"><img src="https://agentmods.dev/badge/skills/desek/outlook-local-mcp/checkpoint-read/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/desek/outlook-local-mcp/checkpoint-read"><img src="https://agentmods.dev/badge/skills/desek/outlook-local-mcp/checkpoint-read.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Tool Misuse · line 65 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00036 | $0.00563 |
| Opus 5.5 | $0.00014 | $0.00225 |
| Sonnet 5.5 | $0.00007 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
checkpoint-read 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/checkpoint-read
Reads checkpoint commit history to recover project context when starting a new session. Queries Git history for checkpoint commits created by /checkpoint-commit, displays the most recent relevant checkpoint details, and summarizes what was implemented, what remains, and any decisions captured — enabling seamless session continuity.
Usage: /checkpoint-read
No arguments required. The command automatically reads the most recent checkpoint commits from local Git history.
Workflow
Follow these steps in order.
Step 1: List Recent Checkpoints
Query Git history for checkpoint commits:
git log --oneline --decorate --grep '^checkpoint.*:' -n 25
- If no results: Report "No checkpoint commits found in this repository." and STOP. Proceed with the session without checkpoint context.
- If results exist: Display the list of recent checkpoint commits to provide an overview of checkpoint history.
Step 2: Read Most Recent Checkpoint
Extract the SHA from the most recent (first) checkpoint in the list, then read its full details:
# Show commit stats (files changed)
git show --stat {SHA}
# Show full commit message and diff
git show {SHA}
Parse the commit message subject line and body for context recovery.
Step 3: Summarize Context
Analyze the checkpoint commit message and produce a structured summary with three sections:
- What was implemented: Extract completed work from the commit body bullet points and diff content.
- What remains: Identify pending items, TODOs, or incomplete work mentioned in the commit message.
- Decisions captured: Note any architectural or design decisions recorded in the commit message.
Step 4: Report
Present the structured summary to the user, including:
- The checkpoint commit SHA and date for reference
- The CR identifier from the commit subject (e.g.,
CR-XXXX) - The three-section context summary (implemented, remaining, decisions)
Safety Rules
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.
- 1mo ago First seen · 69 lines · 36 tokens per session scan A 5bd2d7d06bbc
checkpoint-read is a skill published in the GitHub repository desek/outlook-local-mcp (45 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 563 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-08-30.
Other skills, from other repositories
git-ai-search
Search and restore AI conversation context from git history.
remember
Save the decisions, facts, dead ends and architecture this conversation established to Atlas's shared memory, so other agents and future sessions can build on them.
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.
release
Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.
recall-rationale
Recall why a past change was made by locating the Claude Code transcript that produced it. Use when the user asks to "recall the rationale", "find the rationale", "look up the rationale", "why did I do X", "why did we do X", "why was this changed", or "find the transcript for this commit".
release-finalizer
Merges a release PR, associates it with resolved issues, replies to issue reporters, and closes issues. Use after PR review is complete and ready for merge. Closes the release cycle.