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 disruptorgit 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/disruptor)<a href="https://agentmods.dev/skills/smixs/disruptor-skills/disruptor"><img src="https://agentmods.dev/badge/skills/smixs/disruptor-skills/disruptor/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/disruptor"><img src="https://agentmods.dev/badge/skills/smixs/disruptor-skills/disruptor.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.00034 | $0.02093 |
| Opus 5 | $0.00017 | $0.01046 |
| Sonnet 5 | $0.00007 | $0.00419 |
| Haiku 4.5 | $0.00003 | $0.00209 |
Grade A, and why
disruptor 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 11d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Disruptor
Eleven battle-tested skills that carry an AI-agent-built project from idea to running server, wired into one ordered flow. This skill is the router: it names the stage sequence, the artifact each stage hands the next, and the gates that decide where you go — don't reinvent the skills here.
Core principle: the agent's own sense of "done" is the enemy. Every method exists to outlast a plausible-but-premature stop — an unread green check, a spec with a hidden default, a rubber-stamp review, a loop that only ever adds. Trust the method over the feeling, and the gate over the guess.
The pipeline
0 Setup ─► 1 Design ─► 2 Spec ─► 3 Guardrails ─► 4 Breakdown ─► 5 Build&converge ─► 6 QA ─► 7 Deploy
(once) 7w3 spec arch slices ├ 5a reviewers
│ └ 5b unvibe
G3F ──► 4–5 fleet lane ───────► 6 QA
| # | Stage | Skill | Kind | Consumes → Produces |
|---|---|---|---|---|
| 0 | Setup (once/repo) | setting-up-domain-model |
method | repo → CONTEXT.md + docs/adr/ |
| 1 | Design | designing-with-7w3 |
method | idea/RFC/ticket → 7w3 subject tree |
| 2 | Spec | write-spec |
prompt | design → build-ready spec |
| 3 | Guardrails | architecture-guardrails |
prompt | spec+stack → executable module boundaries |
| 4 | Breakdown | slicing-into-tracer-bullets |
method | spec+arch → ordered vertical slices |
| 5 | Build & converge | converging-and-polishing |
method | one slice → hardened, converged artifact |
| 5a | ↳ Review | spawning-reviewers |
method | settled artifact → located findings |
| 5b | ↳ Cut | unvibe-review |
method | grown artifact → ranked cuts/reframes |
| 4–5 | Fleet lane | delivering-mvp-fleet |
method | spec+slices (or vague idea) → launchable MVP |
| 6 | QA | qa-demo-stand |
prompt | built project → reproduced+fixed defects |
| 7 | Deploy | setup-server |
prompt | QA'd project → safely provisioned server |
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.
- 11d ago First seen · 117 lines · 34 tokens per session scan A b690eeef7367
disruptor is a skill published in the GitHub repository smixs/disruptor-skills (18 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 2,093 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…