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 delivering-mvp-fleetgit 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/delivering-mvp-fleet)<a href="https://agentmods.dev/skills/smixs/disruptor-skills/delivering-mvp-fleet"><img src="https://agentmods.dev/badge/skills/smixs/disruptor-skills/delivering-mvp-fleet/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/delivering-mvp-fleet"><img src="https://agentmods.dev/badge/skills/smixs/disruptor-skills/delivering-mvp-fleet.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.00100 | $0.02442 |
| Opus 5 | $0.00050 | $0.01221 |
| Sonnet 5 | $0.00020 | $0.00488 |
| Haiku 4.5 | $0.00010 | $0.00244 |
Grade A, and why
delivering-mvp-fleet 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MVP Delivery — fleet orchestration from idea to launchable MVP
Stage contract
- Stage: 4–5 alternative (fleet lane)
- Kind: method
- Inputs: a build-ready spec + slices (from the pipeline) OR a vague idea (own on-ramp, Phase 0 interview)
- Outputs: launchable MVP + HTML report + next-batch board nodes
- Entry gate: G3F (parallelizable + fleet budget), or the speed-to-MVP on-ramp
- Done when: board all done, full gate green, one-boot completeness green
- Next: the
qa-demo-standskill
You are the ORCHESTRATOR. You almost never write product code yourself: you interview, plan, decompose, author contracts and mandates, fan out workers, watch the board, absorb pivots, and integrate. The method rests on one belief: an agent with a narrow scope finds more nuance in that scope than a wide-scope agent finds anywhere — provided narrow scopes are made globally coherent by explicit contracts, alignment anchors, and integration tasks.
Everything durable lives ON DISK (plan doc, board, per-task dirs, handoff log) so any harness — or a fresh session after a crash — can resume from the files alone.
Phase 0 — Understand (explore or interview)
If a project exists: explore it (fan out read-only explorers if available; read key docs yourself). If not: run 2–3 SHORT rounds of questions with the user — domain, audience, what "launched and tested" means to them, hard constraints (budget, deadline, tech, brand), what already exists. Stop interviewing when you can write the plan; don't interrogate.
Record durable facts (client pivots, provider constraints) in memory AND in the plan doc — pivots WILL happen mid-build; versioned plan docs (v2, v3…) absorb them cheaply.
Phase 1 — Audiences → personas → user stories → features
Work top-down, breadth first, in the plan doc (copy references/plan-template.md to the
project as PLAN.md — it is the single document every worker reads first). PLAN.md is a
compressed 7w3 root subject (Wish, Boundaries, What's-next are 7w3 facets) — when you
arrive from the full pipeline, derive it from the 7w3 design and spec instead of
re-interviewing.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 165 lines · 100 tokens per session scan A 7a14a5ffd497
delivering-mvp-fleet is a skill published in the GitHub repository smixs/disruptor-skills (18 stars, last pushed 2mo ago), licensed MIT. It adds 100 tokens to every session and 2,442 once invoked, about $0.0005 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…