orch-delivery

orch-delivery is a skill for Claude Code from kninetimmy/orch. It costs 84 tokens per session (6,739 once invoked), scanned A, original, MIT.

A workflow guide for managing an Orch Delivery run, where planned coding issues are assigned, reviewed, and merged.

In plain words
What is it for?
Use it after planning work to start delivery, pass the plan gate, dispatch issues, review changes, merge completed work, and report command results.
Why use it?
It keeps delivery decisions and status tied to the Orch command-line tool, so the workflow follows its rules and results.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions subagents; names the AskUserQuestion tool.

Part of the orch plugin — 3 skills, 3 commands, 5 agents, 2 hooks shipped together

Good fit Use it after planning work to start delivery, pass the plan gate, dispatch issues, review changes, merge completed work, and report command results.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kninetimmy/orch/orch-delivery
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 kninetimmy/orch --skill orch-delivery
Clone the repo
git clone --depth 1 https://github.com/kninetimmy/orch

Made for: Claude Code.

Or install orch, the plugin that ships this one along with the rest of its 3 skills, 3 commands, 5 agents, 2 hooks.

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.

agentmods badge for orch-delivery

README.md
[![agentmods](https://agentmods.dev/badge/skills/kninetimmy/orch/orch-delivery/github.svg)](https://agentmods.dev/skills/kninetimmy/orch/orch-delivery)
Your own site
<a href="https://agentmods.dev/skills/kninetimmy/orch/orch-delivery"><img src="https://agentmods.dev/badge/skills/kninetimmy/orch/orch-delivery/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.

agentmods 80×15 button for orch-delivery

Your own site · 80×15
<a href="https://agentmods.dev/skills/kninetimmy/orch/orch-delivery"><img src="https://agentmods.dev/badge/skills/kninetimmy/orch/orch-delivery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,739 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00084 $0.06739
Opus 5 $0.00042 $0.03370
Sonnet 5 $0.00017 $0.01348
Haiku 4.5 $0.00008 $0.00674

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

Security

Grade A, and why

orch-delivery 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.

adapters/claude/skills/orch-delivery/SKILL.md · 530 lines

How it starts

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

Orch Delivery

This skill is the wire contract and presentation layer for a Delivery run. Every decision (what routes where, what is allowed next, what a gate result means) comes from orch run <verb>; your job is to construct honest requests, run the verb, and present its result faithfully.

The JSON pattern every verb call follows

  1. Write the request JSON to a scratch file in the OS temp directory, outside the repository (never inside the working tree or a worktree).
  2. Run orch run <verb> < <scratch-file> and capture stdout. PowerShell (5.1 and pwsh 7) rejects < ("The '<' operator is reserved for future use."); use the pipe form instead: Get-Content -Raw <scratch-file> | orch run <verb>. On Windows PowerShell 5.1 specifically, that pipe alone silently corrupts non-ASCII (em dashes, §) into ?; guard it with $OutputEncoding = New-Object System.Text.UTF8Encoding $false; Get-Content -Raw -Encoding UTF8 <scratch-file> | orch run <verb>.
  3. Exit 0: parse stdout as the verb's JSON result.
  4. Non-zero exit: the engine refused. Present the stderr message verbatim — never paraphrase, never retry blind, never work around it. Only a revised request (different facts, different approval, a resolved precondition) is a valid next step.

orch run status --json never reads stdin — call it bare.

Selection-bearing wire versions are closed: StatusDoc 2, GateDoc 2, Dispatch 4, Escalate 2, Review 3. Reject any other schema_version before reading or submitting a Selection.

PlanDoc construction

Build a PlanDoc (schema_version: 1) honestly. Routing is derived entirely from the facts you declare; there is no field to choose a model or effort yourself. "Adjust agent routing" at the gate always means: revise the facts that were wrong and resubmit — never hand-edit a routed selection.

{
  "schema_version": 1, "host": "claude", "title": "...", "summary": "...",
  "issues": [{
    "id": "issue-slug", "title": "...", "objective": "...",
    "acceptance_criteria": ["..."], "type": "feature",
    "area_labels": ["..."],
    "facts": {
      "read_only": false, "unusually_difficult": false,
      "risk_domains": [],
      "downgrade": {"mechanical": false, "low_risk": false,
                     "fully_specified": false, "unsurprising": false}
    },
    "depends_on": [], "wave": 1, "required_tests": ["..."],
    "tests_ci_does_not_run": ["..."],
    "usage_class": "medium"
  }]
}

Read the full file on GitHub · 530 lines

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.

  1. 9d ago First seen · 530 lines · 84 tokens per session scan A e9631127e644

Subscribe to this mod's changes

orch-delivery is a skill published in the GitHub repository kninetimmy/orch (21 stars, last pushed 11d ago), licensed MIT. It adds 84 tokens to every session and 6,739 once invoked, about $0.0004 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-08-30.

Related

Other skills, from other repositories