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 execute-taskgit 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/execute-task)<a href="https://agentmods.dev/skills/inkatze/planwright/execute-task"><img src="https://agentmods.dev/badge/skills/inkatze/planwright/execute-task/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/execute-task"><img src="https://agentmods.dev/badge/skills/inkatze/planwright/execute-task.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.00112 | $0.07410 |
| Opus 5.5 | $0.00045 | $0.02964 |
| Sonnet 5.5 | $0.00022 | $0.01482 |
| Haiku 4.5 | $0.00011 | $0.00741 |
Grade A, and why
execute-task 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 5d 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 — 491 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/execute-task
The execution layer of the planwright pipeline (REQ-E1.1–REQ-E1.5): take one
ready unit (a single task or a cohesion bundle) from a Ready or Active spec with
a signed-off kickoff brief and carry it from a failing test to a draft PR.
/orchestrate dispatches it into a prepared worktree; a human may also run it
inside one. It works from the kickoff
brief, the durable contract (D-3), not by re-reading the spec; sign-off and
merge are the human's reserved controls (see Invariants).
Doctrine
This skill is procedure, not doctrine. Read the manifest's rule docs via
scripts/resolve-rule-doc.sh <doc-name> (under the resolved planwright root);
their definitions govern the concepts this skill names. Per
doctrine/instruction-hygiene.md, run-start entries load before work begins,
point-of-use entries at the named step or 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.
If a manifest doc does not resolve — at run start or its point of use — halt
naming the missing doc and the chain consulted (REQ-K1.7). decision-domains
degrades gracefully instead: absent, note it in one line, skip the drift check,
and use engineering judgment.
Doctrine: run-start spec-format (lifecycle, anchors, freshness, commit trailer) Doctrine: run-start proportionality Doctrine: point-of-use research-rigor Doctrine: point-of-use security-posture Doctrine: point-of-use validation-rigor Doctrine: point-of-use finding-categorization Doctrine: point-of-use gate-wiring Doctrine: point-of-use decision-domains Doctrine: point-of-use custom-steps
Pre-flight
Run once per invocation, in order. Any halt records the unit to the spec's
tasks.md ## Awaiting input section with the reason — on a v2 bundle as a
committed reference bullet on the task branch, **Task <id>** — <reason>, the
block staying in ## Tasks (D-3); in a holder or plain store,
scripts/halt-note.sh writes it uncommitted, named in the handoff
(custom-spec-location REQ-E1.9) — and ends the step (the gate-wiring pause
protocol's dispatched arm); attended, present and wait.
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.
- 5d ago Changed · +1 lines · -4 tokens per session 7422c1be2aa4
- 6d ago Changed 3b85a47b7942
- 9d ago Changed bded6b60547d
- 10d ago Changed 484fc0e35b09
- 11d ago Changed dcbbafd3ce5e
- 12d ago Changed · +2 lines 2acf53a19de7
- 14d ago Changed · -2 lines f50d05ca94fe
- 16d ago Changed · +3 lines · +4 tokens per session 97656b060a8d
- 19d ago Changed · -4 lines · +1 tokens per session 4425118d642a
- 23d ago First seen · 491 lines · 111 tokens per session scan A e9443a624be9
execute-task is a skill published in the GitHub repository inkatze/planwright (5 stars, last pushed today), licensed MIT. It adds 112 tokens to every session and 7,410 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.