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 kninetimmy/orch --skill orch-deliverygit clone --depth 1 https://github.com/kninetimmy/orchWrote 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/kninetimmy/orch/orch-delivery)<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.
<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>- NVIDIA SkillSpector pass
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.00084 | $0.06739 |
| Opus 5 | $0.00042 | $0.03370 |
| Sonnet 5 | $0.00017 | $0.01348 |
| Haiku 4.5 | $0.00008 | $0.00674 |
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.
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
- Write the request JSON to a scratch file in the OS temp directory, outside the repository (never inside the working tree or a worktree).
- 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>. - Exit 0: parse stdout as the verb's JSON result.
- 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"
}]
}
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 · 530 lines · 84 tokens per session scan A e9631127e644
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.
Other skills, from other repositories
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
gsd-complete-milestone
Archive completed milestone and prepare for next version.
github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
testdino-releases
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers listreleases, getrelease, createrelease, and updaterelease. Accepts counter-style IDs like MS-12.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.