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-commit/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-commit)<a href="https://agentmods.dev/skills/desek/outlook-local-mcp/checkpoint-commit"><img src="https://agentmods.dev/badge/skills/desek/outlook-local-mcp/checkpoint-commit/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-commit"><img src="https://agentmods.dev/badge/skills/desek/outlook-local-mcp/checkpoint-commit.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 95 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.00046 | $0.00811 |
| Opus 5.5 | $0.00018 | $0.00324 |
| Sonnet 5.5 | $0.00009 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
checkpoint-commit 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/checkpoint-commit
Creates a governance checkpoint commit to preserve work-in-progress state. Analyzes all repository changes, validates .gitignore, and creates a properly formatted commit linked to a Change Request.
Usage: /checkpoint-commit [CR-XXXX] [summary]
Both arguments are optional. The command will auto-detect the CR ID and generate a summary if not provided.
Workflow
Follow these steps in order.
Step 1: Context Detection
Determine the CR identifier:
- If CR-ID is provided in
$ARGUMENTS: Use the provided CR-ID. - If CR-ID is NOT provided:
- Check the current Git branch name for a pattern like
dev/CR-XXXXor any branch containingCR-followed by digits. - If not found in branch name, check the most recently modified file in
docs/cr/usinggit log --diff-filter=M -1 --name-only -- docs/cr/. - If the CR-ID is ambiguous or cannot be determined, MUST prompt the user for confirmation. Do NOT proceed without a confirmed CR-ID.
- Check the current Git branch name for a pattern like
Step 2: Analyze Changes
Examine all changes in the repository:
# Staged changes
git diff --staged
# Unstaged changes
git diff
# Untracked files
git ls-files --others --exclude-standard
- MUST identify all staged, unstaged, and untracked files.
- If there are no changes (no staged, unstaged, or untracked files), report "No changes to checkpoint" and stop. Do NOT create a commit.
Step 3: Update .gitignore
Before staging, review untracked files and update .gitignore to exclude:
- Temporary files (
.tmp,.bak,*.log) - Build artifacts (
dist/,build/,node_modules/) - Generated content (compiled files, cache directories)
- IDE-specific files not already covered
This step is mandatory to prevent repository bloat. If more than 50 untracked files are detected, MUST confirm with the user before proceeding.
Step 4: Write Summary
- If summary is provided in
$ARGUMENTS: Use the provided summary. - If summary is NOT provided: Analyze the diff output and generate a "Golden Summary" — a concise one-sentence description of the changes.
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 · 100 lines · 46 tokens per session scan A 6a3cadd4d072
checkpoint-commit is a skill published in the GitHub repository desek/outlook-local-mcp (45 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 811 once invoked, about $0.0002 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…