What is orchestration-commands?

A registry that lists available orchestration commands and explains what each command is for and where its instructions are stored.

Use it to find the right command skill for a coding workflow and understand its purpose before invoking it.

It gives developers one place to discover the commands available for planning, testing, reviews, fixes, documentation, and status checks.

orchestration-commands — Skill for Claude Code and Codex by mattmre

Install

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.

Any agent

npx skills add mattmre/EVOKORE-MCP-PUBLIC --skill commands

Clone the repo

git clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLIC

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/commands/github.svg)](https://agentmods.dev/skills/mattmre/evokore-mcp-public/commands)

Your own site

<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/commands"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/commands/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/commands"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/commands.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 808 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00808
Opus 5	$0.00008	$0.00404
Sonnet 5	$0.00003	$0.00162
Haiku 4.5	$0.00002	$0.00081

Measured 7d ago against content hash a4ecf33af909, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

orchestration-commands 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.

SKILLS/ORCHESTRATION FRAMEWORK/commands/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Orchestration Command Registry

This registry defines all available orchestration command skills. Each command is a standalone skill that can be invoked independently.

Available Commands

Command	Purpose	Skill Path
`orch-status`	Review runtime state and surface blockers	orch-status/SKILL.md
`orch-tasks`	List and manage open tasks with priorities	orch-tasks/SKILL.md
`orch-verify`	Capture verification evidence for current task	orch-verify/SKILL.md
`orch-handoff`	Generate session wrap summaries	orch-handoff/SKILL.md
`orch-plan`	Create approval-gated implementation plans	orch-plan/SKILL.md
`orch-review`	Trigger code review with risk routing	orch-review/SKILL.md
`orch-tdd`	RED/GREEN/REFACTOR workflow entry point	orch-tdd/SKILL.md
`orch-build-fix`	Diagnose and fix build/test failures	orch-build-fix/SKILL.md
`orch-refactor`	Dead code cleanup and refactoring	orch-refactor/SKILL.md
`orch-docs`	Documentation synchronization	orch-docs/SKILL.md
`orch-e2e`	Generate and run E2E test suites	orch-e2e/SKILL.md

Schema

Each command skill follows this schema:

id: string           # Unique identifier (orch-prefixed)
name: string         # Display name
description: string  # Brief purpose statement
triggers:            # What invokes this command
  - manual           # Operator-initiated
  - scheduled        # Time-based
  - event            # Triggered by system event
inputs:              # Required context
  - document: string # Input path or description
    required: bool   # Whether mandatory
outputs:             # Produced artifacts
  - document: string # Output path or pattern
    action: string   # create | update | append

Read the full file on GitHub · 86 lines

Files

What ships with it

30 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.

Changes

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 · 86 lines · 15 tokens per session scan A a4ecf33af909

Subscribe to this mod's changes

orchestration-commands 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 808 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.

Building agents Productivity agentic-ai aggregator ai-tools claude hitl mcp orchestration-framework

todos

This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…

JetBrains/thinkrail · 127 tokens

handoff

Checkpoint work for recovery — fires on "handoff", "wrap up", context pressure, a closed phase, or before a long external wait or irreversible gate. Part of the Agentsmith harness; writes durable state plus a paste-ready kickoff block so a fresh session loses nothing.

PromptPartner/agentsmith · 58 tokens

orchestration-commands