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 designing-with-7w3git 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/designing-with-7w3)<a href="https://agentmods.dev/skills/smixs/disruptor-skills/designing-with-7w3"><img src="https://agentmods.dev/badge/skills/smixs/disruptor-skills/designing-with-7w3/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/designing-with-7w3"><img src="https://agentmods.dev/badge/skills/smixs/disruptor-skills/designing-with-7w3.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.00123 | $0.03852 |
| Opus 5 | $0.00062 | $0.01926 |
| Sonnet 5 | $0.00025 | $0.00770 |
| Haiku 4.5 | $0.00012 | $0.00385 |
Grade A, and why
designing-with-7w3 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 12d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
7w3 Driven Development
Stage contract
- Stage: 1. Design · Kind: method
- Inputs: an idea / RFC / ticket / feature request (from a router on-ramp).
- Outputs: a 7w3 subject tree — each subject's ten facets, grounded in real things.
- Entry gate: you're moving from "what we want" to "how it works"; the repo's
conventions/CONTEXT.md exist (else invoke the
setting-up-domain-modelskill first). - Done when: every leaf subject answers all ten facets (or an explicit
n/a — because…), Where/Who/When cite real files/names/events, no unacknowledged holes remain. - Next: the
write-specskill — turn the settled design into a canonical spec. - Maintains: CONTEXT.md (cite/sharpen terms) · ADRs (record hard-to-reverse design decisions).
7w3 is a way to design anything by describing each subject completely along ten facets, and keeping all ten together in one place. It is similar in spirit to user-story-driven development and BDD — but where a user story captures only the wish and BDD captures only the when/how of a scenario, 7w3 insists you capture the whole subject: who owns it, where it lives, when it fires, why it exists, what it is not, what it can't do, and what happens next — all at once, so the subject can be reasoned about, reviewed, and implemented as a single coherent unit.
The name: 7 Ws + 3 = ten facets.
When to use this
Use 7w3 the moment you move from "what do we want" to "how will this actually work": designing a feature or subsystem, an API, a protocol, a refactor, a migration, an org process, a decision record. Use it to turn a vague spec/RFC/ticket into something implementable. Use it instead of jumping straight to a phased to-do list — phases flatten the decision structure that 7w3 preserves.
It is general-purpose: nothing about it is tied to code. A hiring process, a kitchen remodel, and a rate limiter can all be 7w3 subjects.
The ten facets
The Seven Ws
| facet | the question it answers | a good answer | the hole it exposes when empty |
|---|---|---|---|
| Wish | What outcome do we want? What is success? | a desired end state, not a mechanism | you're building without knowing what "done" means |
| Why | Why does this matter? Why this way? | motivation + reason + causes + intentions | you can't tell which constraints are real |
| What | What is this, exactly? | a precise definition of the one thing | if there are two "whats", it's two subjects |
| Who | Who is responsible / who acts / who's affected? | named actors + their roles | nobody owns it, or everybody does |
| Where | Where does it live? (file, system, place, context) | concrete locations — grounded, not "somewhere" | it can't be found or built |
| When | When does it fire? In what order? What is the lifecycle? | triggers, sequencing, timing, state transitions | races, missed triggers, undefined ordering |
| What's-next | What does this cause downstream? What follows? | implications, ripple effects, dependencies, next steps | surprises land on whoever ships it |
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.
- 12d ago First seen · 250 lines · 123 tokens per session scan A 1a5d05b97b72
designing-with-7w3 is a skill published in the GitHub repository smixs/disruptor-skills (18 stars, last pushed 2mo ago), licensed MIT. It adds 123 tokens to every session and 3,852 once invoked, about $0.0006 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
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.
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.
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…