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 smixs/disruptor-skills --skill write-specgit clone --depth 1 https://github.com/smixs/disruptor-skillsWrote 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/smixs/disruptor-skills/write-spec)<a href="https://agentmods.dev/skills/smixs/disruptor-skills/write-spec"><img src="https://agentmods.dev/badge/skills/smixs/disruptor-skills/write-spec/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/smixs/disruptor-skills/write-spec"><img src="https://agentmods.dev/badge/skills/smixs/disruptor-skills/write-spec.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.00035 | $0.05171 |
| Opus 5 | $0.00017 | $0.02586 |
| Sonnet 5 | $0.00007 | $0.01034 |
| Haiku 4.5 | $0.00003 | $0.00517 |
Grade A, and why
write-spec 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 — 865 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write spec
Stage contract
- Stage: 2. Spec · Kind: prompt
- Inputs: the 7w3 design (stage 1) + known stack/constraints.
- Outputs: a canonical, build-ready specification — every behavior stated; anything unspecified must not be silently invented at build time.
- Entry gate: the design is settled (7w3's done-gate met).
- Done when: DB, backend, UI, integrations, tests, and security can all be built from it without verbal clarification.
- Next: the
architecture-guardrailsskill. - Maintains: uses CONTEXT.md vocabulary; surface new decisions as ADRs.
- Note: this file is a prompt template — everything below the line is the prompt.
Fill its
<placeholders>with the design's facts and hand the whole thing to a fresh executor agent; don't paraphrase it.
You act as the product's chief architect, systems analyst, and technical lead. Your task is to prepare not an overview and not a marketing description, but a canonical implementation specification from which the team and AI agents can build the product without constant verbal clarifications.
Write the specification in the language the user works in (<language> placeholder, default: the language of the input design), in plain understandable language, but with sufficient technical precision. If you use a technical term, explain it immediately in simple words. Do not write generic phrases like "security needs to be thought through". Instead, pin down concrete rules, tables, states, constraints, checks, and readiness criteria.
Input Data
Product: <product name>
Short description: <what the product does and for whom>
Target audience: <who the users, customers, administrators, external participants are>
Specification language: <language; default: the language of the input design>
Current implementation stage: <e.g.: Phase 1 / MVP / first production release / pilot>
What is definitely in scope for the current stage:
<item><item><item>
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 · 865 lines · 35 tokens per session scan A 4f55d67a4d86
write-spec is a skill published in the GitHub repository smixs/disruptor-skills (18 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 5,171 once invoked, about $0.0002 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
debug
Run /debug to find and fix a bug's root cause: a test failing for an unclear reason, /check verify finding a failure, or behavior being wrong. Runs a reproduce, localize, hypothesize, test, fix, verify loop, makes the minimal fix, and hands a regression test to /test. No features, no extra refactors.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
setting-up-a-project
Use whenever asked to set up, onboard, initialize, or spec a project — the front door when the workspace has no spec graph yet (brand-new or an existing codebase); also seeded by the app's Set-up-project card (/skill:setting-up-a-project). Not for feature work in an already-specced project — use the brainstorming…
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
animate
Build a web animation: whether it should animate at all, the purpose, the tool, the properties, the easing curve, the duration, interruption and exit. Writes the CSS or Motion code for dropdowns, modals, toasts, tooltips, accordions, press feedback, stagger and scroll reveals. Use to animate something or make a…