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-tasksgit 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-tasks)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/orch-tasks"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/orch-tasks/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-tasks"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/orch-tasks.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.00015 | $0.00682 |
| Opus 5 | $0.00008 | $0.00341 |
| Sonnet 5 | $0.00003 | $0.00136 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
orch-tasks 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestration Tasks
Purpose
List open tasks with their priorities, status, and acceptance criteria.
Invocation
orch-tasks [filter]
Arguments
| Argument | Required | Description |
|---|---|---|
| filter | No | Status filter: all, queued, in_progress, blocked, review |
Default: Shows queued and in_progress tasks.
Workflow
1. Context Load
Read the following project documents:
- Task queue (e.g.,
TASKS.md) - Priorities list (e.g.,
PRIORITIES.md) - Definition of done / acceptance standards
2. Task Parsing
Extract task entries with fields:
- ID: Task identifier
- Description: Task summary
- Status: Current state (queued, in_progress, blocked, review, done)
- Priority: Priority level or inline priority marker
- Owner: Assigned agent or operator
- Acceptance Criteria: Success conditions
3. Priority Ordering
Order tasks by:
- Priority level (P0 > P1 > P2 > P3)
- Status (in_progress > blocked > queued)
- Creation date (oldest first within same priority)
4. Output Generation
Produce a structured task list:
## Open Tasks
### In Progress
| ID | Description | Owner | Priority | Blockers |
|----|-------------|-------|----------|----------|
| T-001 | [description] | [owner] | P1 | None |
### Queued
| ID | Description | Priority | Est. Effort |
|----|-------------|----------|-------------|
| T-002 | [description] | P2 | 2h |
### Blocked
| ID | Description | Blocked By | Duration |
|----|-------------|------------|----------|
| T-003 | [description] | T-001 | 4h |
---
## Acceptance Criteria (Next Task)
**T-002**: [task description]
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
Outputs
| Output | Destination | Action |
|---|---|---|
| Task list | stdout | display |
This command does not modify project documents; it is read-only.
Status Definitions
| Status | Description |
|---|---|
queued |
In queue, not started |
in_progress |
Active work underway |
blocked |
Waiting on dependency or decision |
review |
Awaiting reviewer input |
done |
Verified and documented |
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 · 117 lines · 15 tokens per session scan A 43d1325ad19a
orch-tasks is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 15 tokens to every session and 682 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).