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 inkatze/planwright --skill orchestrategit clone --depth 1 https://github.com/inkatze/planwrightWrote 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/inkatze/planwright/orchestrate)<a href="https://agentmods.dev/skills/inkatze/planwright/orchestrate"><img src="https://agentmods.dev/badge/skills/inkatze/planwright/orchestrate/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/inkatze/planwright/orchestrate"><img src="https://agentmods.dev/badge/skills/inkatze/planwright/orchestrate.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.00102 | $0.07052 |
| Opus 5.5 | $0.00041 | $0.02821 |
| Sonnet 5.5 | $0.00020 | $0.01410 |
| Haiku 4.5 | $0.00010 | $0.00705 |
Grade A, and why
orchestrate 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 — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orchestrate
The orchestration layer of the planwright pipeline (REQ-F1.1–REQ-F1.10): a
stateless step machine (D-7) advancing a Ready or Active spec one unit per
step (read tasks.md, select, record the dispatch, dispatch /execute-task,
exit). The step is the unit of crash-safety (D-8); progress state is a
derived projection (D-1), so the tower is disposable (D-38), safe under
headless cron and concurrent towers on one spec.
Doctrine
This skill is procedure, not doctrine. Resolve rule docs via
scripts/resolve-rule-doc.sh <doc-name> (under the resolved planwright root);
their definitions govern wherever this skill names a concept. The manifest below
marks which load at run start and which at the named step/branch:
Invoking plugin scripts (REQ-D1.1, D-7). Call scripts/<name>.sh by the
resolved literal absolute path (never $VAR/scripts/<name>.sh), one plain
command per Bash call — doctrine/plugin-script-invocation.md.
Doctrine: run-start proportionality Doctrine: point-of-use selection-contract (candidacy semantics + the selector exit contract) Doctrine: point-of-use spec-format (pre-flight brief check + the freshness gate) Doctrine: point-of-use gate-wiring (recording a halt to Awaiting input) Doctrine: point-of-use accumulator-taxonomy (--bookkeeping / gate drain) Doctrine: point-of-use context-budget-autoheal (the --watch long-running loop) Doctrine: point-of-use inter-orchestrator-coordination (worker relay / merged-window cleanup) Doctrine: point-of-use orchestration-concurrency (dispatch record + reconcile sweep) Doctrine: point-of-use orchestration-modes (--meta / --fleet / --bookkeeping / degradation & failover) Doctrine: point-of-use tower-comms (how the loop's turns speak to the operator)
On a dispatch path (selecting and dispatching a unit), a missing core doc
fails closed (REQ-K1.7). Halt, naming the missing doc and the chain consulted.
On non-dispatching paths (--bookkeeping, a read-only status step) it
degrades — note it in one line and continue.
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 Changed · -50 lines e6bc8237a8d8
- 9d ago Changed ddde427b6b72
- 10d ago Changed · +4 lines df8bf818e738
- 11d ago Changed · +1 lines 0a81e8a1a27d
- 12d ago Changed 14b52e1152b9
- 14d ago Changed · +8 lines 52c893386a74
- 16d ago Changed 4b0c9f705cb9
- 19d ago Changed 7ef8816333c6
- 23d ago Changed 547083b46968
- 25d ago First seen · 500 lines · 102 tokens per session scan A 8a04d0263ac4
orchestrate is a skill published in the GitHub repository inkatze/planwright (5 stars, last pushed today), licensed MIT. It adds 102 tokens to every session and 7,052 once invoked, about $0.0004 per session on Opus 5.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-31.
Other skills, from other repositories
role-activation
Use at project start — /app-init, /app-onboard, or /app-run's first step — to decide which of the roles this product actually needs, and to write the durable roster the rest of the flow reads. Triggers whenever a command is about to fan out to a team, or a gate is about to run for a role that may not be on this…
defect-hunting
Use when reviewing code, auditing an app, writing a guard rule or test, or certifying any threshold/constant/formula. Finds the defects a diff review structurally cannot see — the second write path, the mis-calibrated constant, the rule that cannot fail. Triggers from code-reviewer, /app-audit, qa-engineer…
mutation-testing
Use when adding or reviewing a gate, guard rule, CI grep, or test assertion in this plugin's own scripts — and whenever a suite is green and you need to know whether that means anything. Runs scripts/mutate.sh, which breaks the code on purpose and reports which assertions failed to notice. Triggers from code-reviewer…
architecture-builder
Use to produce the technical architecture doc and engineering principles for a mobile app. Used primarily by the CTO agent. Triggers on "design the architecture", "pick the stack", or as part of /app-plan.
performance-review
Use as a review dimension on any diff that could cost startup time, frames, memory, battery, bandwidth or bundle size — by code-reviewer during review and by web-developer and test-automation-engineer before claiming a UI or harness ticket done. The studio's position is that this is a dimension with existing auditors…
accessibility-gate
Use as a pass/fail gate on any diff with a user-facing surface — by code-reviewer during review, by qa-engineer during the test pass, and by any IC before claiming a UI ticket done. This is the gate the plan called for instead of an accessibility specialist role. Triggers whenever a screen, component or state changes.