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 orch-handoffgit 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/orch-handoff)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/orch-handoff"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/orch-handoff/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/orch-handoff"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/orch-handoff.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.00783 |
| Opus 5 | $0.00009 | $0.00392 |
| Sonnet 5 | $0.00004 | $0.00157 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
orch-handoff 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 9d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestration Handoff
Purpose
Generate a session wrap summary for the next session, documenting current state, decisions made, and recommended next steps.
Note: This skill complements the existing
session-wrapskill inSKILLS/GENERAL CODING WORKFLOWS/session-wrap/. Whilesession-wrapfocuses on the git commit, PR, and session log workflow,orch-handofffocuses on synthesizing orchestration state (tasks, decisions, blockers, plans) into a structured handoff document for session continuity.
Invocation
orch-handoff [notes]
Arguments
| Argument | Required | Description |
|---|---|---|
| notes | No | Additional context or notes to include |
Workflow
1. Context Load
Read the following project state documents:
- Status/state tracking document (e.g.,
STATUS.md) - Task queue (e.g.,
TASKS.md) - Decision log (e.g.,
DECISIONS.md) - Current plan (e.g.,
PLAN.md) - Priorities list (e.g.,
PRIORITIES.md)
2. Session Analysis
Synthesize session activity:
- Completed Tasks: Tasks moved to
donethis session - Active Work: Tasks still
in_progress - Decisions Made: Entries added to decision log
- Blockers Encountered: Issues that slowed progress
- Plan Changes: Modifications to the plan
3. Next Actions Derivation
Determine recommended next steps:
- Priority tasks from priorities list
- Unblocked tasks ready for work
- Review items awaiting input
- Follow-up actions from decisions
4. Handoff Generation
Produce a structured session wrap:
## Session Wrap: [YYYY-MM-DD HH:MM]
### Status Summary
**Session Duration**: [start] - [end]
**Tasks Completed**: [count]
**Tasks In Progress**: [count]
**Blockers**: [count]
### Completed This Session
- [x] [task-id]: [description]
- [x] [task-id]: [description]
### Still In Progress
- [ ] [task-id]: [description] - [status note]
### Decisions Made
| Decision | Rationale | Impact |
|----------|-----------|--------|
| [decision] | [why] | [what changes] |
### Blockers & Issues
- [blocker description and mitigation]
### Recommended Next Steps
1. **[Priority]**: [action description]
2. **[Priority]**: [action description]
3. **[Priority]**: [action description]
### Notes
[Additional context or operator notes]
---
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.
- 9d ago First seen · 126 lines · 18 tokens per session scan A 4b4f93927dee
orch-handoff 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 783 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
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
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.
stakeholder-alignment
Build alignment artifacts — responsibility matrices, decision rights, and communication plans. Use when unclear ownership stalls decisions. For persuading in the moment, use design-negotiation (designer-toolkit).
wrongstack-kanban
Record substantial project work on WrongStack's IPC-backed Kanban board so it survives the session and other agents can see it. Covers card detail, the managed Backlog→Todo→Running→Review→Done lifecycle, lease-fenced dispatch, and what "verified" means before a card reaches Done.
shared-monorepo-nx
Nx monorepo build system — workspace configuration, project graph, task pipelines, caching, generators, plugins, and release management.
shared-monorepo-pnpm-workspaces
Skill "shared-monorepo-pnpm-workspaces" from agents-inc/skills, covering pnpm workspaces for monorepo management, critical: before using this skill, philosophy, core patterns and pattern 1: workspace configuration (pnpm-workspace.yaml).