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 agentmods add skills/inkatze/planwright/orchestratenpx skills add inkatze/planwright --skill orchestrategit clone --depth 1 https://github.com/inkatze/planwrightWhat 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 | $0.00101 | $0.07826 |
| Opus 5 | $0.00051 | $0.03913 |
| Sonnet 5 | $0.00020 | $0.01565 |
| Haiku 4.5 | $0.00010 | $0.00783 |
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 2d 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 — 485 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 — not the session — is the unit of crash-safety (D-8): progress
state is a derived projection (D-1) rebuilt from durable evidence (git
branches, Planwright-Task trailers, runtime markers, gh, the process list),
so a step may die mid-flight without losing work; the committed tasks.md
sections are a discardable snapshot the reconcile sweep rebuilds. The tower is
disposable (D-38): no in-memory state beyond the current step, 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 —
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 / degradation & failover)
On a dispatch path (selecting and dispatching a unit), a missing core doc
fails closed (REQ-K1.7) — the defining rules can't be read. Halt, naming the
missing doc and the chain consulted. On non-dispatching paths
(--bookkeeping, a read-only status step), a missing doc 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.
- 2d ago First seen · 485 lines · 101 tokens per session scan A 4d8fd07dae62
orchestrate is a skill published in the GitHub repository inkatze/planwright (3 stars, last pushed 4d ago), licensed MIT. It adds 101 tokens to every session and 7,826 once invoked, about $0.0005 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-31.
Other skills, from other repositories
create-coordclaw-team
A Skill for creating a CoordClaw multi-agent collaborative team. Through an 8-step standardized process, from requirement gathering to team validation, rapidly build a complete AI team.
deploy-agent
Deploy Bindu agents to various environments with safety checks and verification.
add-example-agent
Add a new self-contained example agent under examples/. Use when asked to "create an example for ", "add a tutorial agent", "demo integration with ", or when showcasing a new pattern users should copy.
visionclaw
Hosted at: https://agenticcorporation.net Discovery: GET /api/v1 (returns the live contract) Source / fork it: https://github.com/Huskyauto/VisionClaw-Agent-Public-Release License: Apache 2.0 · v1.0 shipped Apr 21, 2026.
autopilot
Autonomous orchestrator that delegates a task to a /pi, /opencode, /codex, or /cursor subagent and drives it to completion without user babysitting. Invoked as /autopilot . Arms a backgrounded wait for an instant completion ping, checkpoints the subagent every 10 minutes (interrupt, progress report, course-correct)…
agy
Delegate a coding task to an agy (Antigravity CLI) session managed via tmux. Invoke explicitly as $agy. User drives all progress checks and interventions — no auto-polling.