Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICnpx agentmods add skills/mattmre/evokore-mcp-public/session-checkpointWrote 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/mattmre/evokore-mcp-public/session-checkpoint)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/session-checkpoint"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/session-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/mattmre/evokore-mcp-public/session-checkpoint"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/session-checkpoint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00038 | $0.00426 |
| Opus 5 | $0.00019 | $0.00213 |
| Sonnet 5 | $0.00008 | $0.00085 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
session-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 6d 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.
What it actually says
/session-checkpoint — Create Session Checkpoint
Saves a timestamped snapshot of the current session's task status, evidence summary, and purpose to docs/session-logs/session-checkpoint-<ts>.md.
Usage
/session-checkpoint
node scripts/session-checkpoint.js
node scripts/session-checkpoint.js --session <session-id> --out <output-dir>
What it does
- Reads current tilldone task list from
~/.evokore/sessions/{sessionId}-tasks.json - Reads evidence log from
~/.evokore/sessions/{sessionId}-evidence.jsonl - Reads session purpose from the session manifest
- Computes metrics: task completion rate, test pass rate, git op count
- Writes
docs/session-logs/session-checkpoint-{timestamp}.md
Output
A markdown checkpoint file containing:
- Task progress table (completed/pending)
- Evidence summary (test results, git ops, edit traces)
- Recent git operations (last 5)
- Resume instructions for the next session
When to use
- Before a long break (context will be lost)
- Before context compaction (pre-compact hook)
- After completing a major phase
- At the end of each session (in addition to session-wrap)
- Before handing off to another agent or session
Integration
- Works with purpose-gate.js: checkpoint path can be injected into additionalContext
- Used by AGT-013 (Loop Operator) to anchor recovery evidence
/scope-lockuses the checkpoint as its baseline state
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.
- 6d ago First seen · 52 lines · 38 tokens per session scan A 64e9d168a3c8
session-checkpoint is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 426 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-09-03.
Other skills, from other repositories
checkpoint-management
Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.
git-flow
Use this skill when proposing, reviewing, or troubleshooting git commits, branches, pull requests, or merge strategies in a WrongStack project session. Triggers: user mentions "commit", "branch", "PR", "merge", "rebase", "stash", "diff".
shared-tooling-git-hooks
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.
git-workflow
Branching strategies, conventional commits, PR templates, and merge vs rebase guidance. Activate when starting features, creating PRs, or managing releases.
ship
Commit, push, create PR(s), and auto-finalize — full automation pipeline. Handles uncommitted changes and recently created PRs.
save
Lightweight incremental checkpoint for a long autonomous run — refresh the handoff, commit converged work, and push, fired frequently (after each subagent merge, periodically, and when nearing the rate-limit → then ScheduleWakeup past the window reset). Complements /pause (deliberate one-shot handoff) and /resume (the…