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-plangit 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-plan)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/orch-plan"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/orch-plan/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-plan"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/orch-plan.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.00016 | $0.00796 |
| Opus 5 | $0.00008 | $0.00398 |
| Sonnet 5 | $0.00003 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
orch-plan 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 8d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestration Plan
Purpose
Create an implementation plan for a request, breaking it into phases and tasks with acceptance criteria, then wait for operator approval before execution.
Invocation
orch-plan <request>
Arguments
| Argument | Required | Description |
|---|---|---|
| request | Yes | Description of what needs to be implemented |
Workflow
1. Context Load
Read the following:
- Existing task queue (e.g.,
TASKS.md) - Current plan state (e.g.,
PLAN.md) - Priority context (e.g.,
PRIORITIES.md) - Acceptance standards (if defined)
2. Request Analysis
Analyze the request to determine:
- Scope: What is being requested
- Dependencies: What must exist or complete first
- Risk Triggers: Security, API, schema, or other review triggers
- Effort Estimate: Approximate complexity
3. Plan Generation
Create structured implementation plan:
## Plan: [Request Title]
**Created**: [YYYY-MM-DD HH:MM]
**Status**: PENDING_APPROVAL
### Objective
[Clear statement of what this plan achieves]
### Scope
**In Scope**:
- [item]
- [item]
**Out of Scope**:
- [item]
### Phases
#### Phase 1: [Phase Name]
**Objective**: [phase goal]
**Estimated Effort**: [time estimate]
**Tasks**:
- [ ] [task description]
- [ ] [task description]
**Acceptance Criteria**:
- [ ] [criterion]
- [ ] [criterion]
**Risk Triggers**: [none | list triggers]
#### Phase 2: [Phase Name]
[...]
### Dependencies
- [dependency and resolution approach]
### Review Requirements
| Phase | Review Type | Reviewer |
|-------|-------------|----------|
| 1 | [type] | [role] |
### Rollback Strategy
[How to revert if issues arise]
---
**AWAITING APPROVAL**
Reply with:
- `approve` - Proceed with implementation
- `modify` - Request changes to plan
- `reject` - Cancel this plan
4. Confirmation Wait
Critical: Do not proceed with implementation until operator provides explicit approval.
Wait states:
approve/yes/proceed: Begin execution, update plan status toAPPROVEDmodify/change: Request clarification, regenerate planreject/cancel/no: Abort, discard plan
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.
- 8d ago First seen · 152 lines · 16 tokens per session scan A 4c0da246c8ef
orch-plan is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 796 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).