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 skills add mattmre/EVOKORE-MCP-PUBLIC --skill handoff-protocolgit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/handoff-protocol)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/handoff-protocol"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/handoff-protocol/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/handoff-protocol"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/handoff-protocol.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.00018 | $0.00743 |
| Opus 5 | $0.00009 | $0.00371 |
| Sonnet 5 | $0.00004 | $0.00149 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
handoff-protocol 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 7d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff Protocol
A structured protocol for managing multi-session agent orchestration. This protocol ensures continuity between sessions, captures evidence of work performed, and provides templates for common orchestration activities.
Overview
The handoff protocol defines how agents pass context between sessions. It covers:
- Session state: What was done, what is in progress, what is next
- Evidence capture: Commands run, outputs observed, artifacts created
- Review workflows: When and how to request reviews
- Escalation paths: When to escalate issues to higher authority
Documents
Core State Files
| Document | Purpose |
|---|---|
| STATUS.md | Runtime assumptions, constraints, and current context |
| PLAN.md | Objectives, success criteria, and project-level constraints |
| TASKS.md | Task queue, status tracking, and task template |
| DECISIONS.md | Architecture decision log with rationale |
| PRIORITIES.md | Rolling horizon priorities (2-4 week window) |
Workflow Guides
| Document | Purpose |
|---|---|
| SPEC_FIRST_CHECKLIST.md | Pre-implementation checklist to lock scope and acceptance criteria |
| AUTONOMY_BUDGET.md | Per-task scope, allowed actions, and escalation triggers |
| HARNESS_INITIALIZER.md | Session initialization steps and clean-state protocol |
| PROGRESS_LOG_FORMAT.md | Progress log fields and rotation guidance |
Evidence and Review
| Document | Purpose |
|---|---|
| EVIDENCE_CAPTURE.md | Template for recording commands and verification outcomes |
| REVIEW_CAPTURE.md | Template for capturing review inputs and resolutions |
| REVIEW_CHECKLIST.md | Quick-reference review checklist with risk triggers |
| SESSION_WRAP.md | End-of-session wrap-up template |
What ships with it
15 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.
- AUTONOMY_BUDGET.md 793 B
- DECISIONS.md 357 B
- DEFINITION_OF_DONE.md 584 B
- ESCALATION_PATHS.md 868 B
- EVIDENCE_CAPTURE.md 1.9 KB
- HARNESS_INITIALIZER.md 918 B
- PLAN.md 2.0 KB
- PRIORITIES.md 377 B
- PROGRESS_LOG_FORMAT.md 820 B
- REVIEW_CAPTURE.md 1.3 KB
- REVIEW_CHECKLIST.md 1.1 KB
- SESSION_WRAP.md 1.1 KB
- SPEC_FIRST_CHECKLIST.md 1.0 KB
- STATUS.md 1.8 KB
- TASKS.md 2.1 KB
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.
- 7d ago First seen · 74 lines · 18 tokens per session scan A 465ef4a3116a
handoff-protocol is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 743 once invoked, about $0.0001 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
morning
Use when performing daily status check-ins, PR reviews, and morning workflow routines.
brain-capture
Quickly capture tasks, ideas, and notes with smart metadata inference. Use when the user says "remind me", "save this", "add a task", "I need to", "don't let me forget", or any variant of quick capture.
team-workflow
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use design-sprint-plan.
03_task5
Triages a support inbox, prioritizes urgent issues, routes each to the right internal team member, and drafts any customer-facing replies for review. Use when: catching up on a backlog of support messages, producing an escalation report, or routing issues to appropriate owners.
03_task2
Extracts action items and pending tasks from Slack messages. Use when: reviewing unread messages for todos, finding deadlines or requests directed at the user, or producing a task summary from recent Slack activity.
lark-workflow-standup-report
A workflow that combines calendar events with unfinished Lark tasks to produce a daily or weekly work summary.