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 spec-kickoffgit 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/spec-kickoff)<a href="https://agentmods.dev/skills/inkatze/planwright/spec-kickoff"><img src="https://agentmods.dev/badge/skills/inkatze/planwright/spec-kickoff/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/spec-kickoff"><img src="https://agentmods.dev/badge/skills/inkatze/planwright/spec-kickoff.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.00108 | $0.07056 |
| Opus 5.5 | $0.00043 | $0.02822 |
| Sonnet 5.5 | $0.00022 | $0.01411 |
| Haiku 4.5 | $0.00011 | $0.00706 |
Grade A, and why
spec-kickoff 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 6d 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 — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spec-kickoff
The comprehension layer of the planwright pipeline (REQ-B2.4, REQ-B2.2):
a section-by-section walkthrough of a spec bundle until human and agent
hold the same understanding, recorded as <root>/<spec>/kickoff-brief.md —
the durable contract (two-brief model, D-3). Downstream skills
(/execute-task, /orchestrate) operate from the brief, not the spec; what
this walkthrough gets wrong, execution gets wrong.
Sign-off is the first key of a two-key launch (D-44): it flips the spec Draft→Ready and, on a clean completion, marks the spec PR ready (D-6, D-7; the walkthrough is the bundle's review). The human's merge is the second key, making the Ready spec operational (the first dispatch derives Active, not this skill). This skill marks only the spec PR ready, never merges, never dispatches execution.
Doctrine
This skill is procedure, not doctrine. Resolve and read the run-start rule
docs via the rule-doc resolution convention
(scripts/resolve-rule-doc.sh <doc-name> under the resolved planwright
root); their definitions govern wherever this skill names a concept:
security-posture— artifact data-hygiene.
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.
spec-format (pre-flight step 2) — the meta-spec: bundle format, status
lifecycle, amendment ritual, sign-off records, content anchors, and sanctioned
anchor command forms. This skill is the writer its sign-off rules name; it
follows them exactly. Three more, at Sign-off step 1:
discovery-rigor— the lens checklist, coverage table, and fan-out behind the lens review.autopilot-reflex— the altitude gate (D-11) behind the altitude check.validation-rigor— validation of lens findings before disposition.
If any of those five does not resolve — at run start or point of use — halt naming the missing doc and the chain consulted (REQ-K1.7). The rest degrade gracefully instead:
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.
- 6d ago Changed · +2 lines f484bfd844f0
- 11d ago Changed d5c8c5e9f16b
- 12d ago Changed c0032d1d573d
- 27d ago Changed 550b55a9dcac
- 1mo ago Changed · +1 lines 3df79204bedb
- 1mo ago Changed · +2 lines df30553e8bf7
- 1mo ago First seen · 444 lines · 108 tokens per session scan A 205d6a9570ea
spec-kickoff is a skill published in the GitHub repository inkatze/planwright (5 stars, last pushed today), licensed MIT. It adds 108 tokens to every session and 7,056 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.