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 alexclowe/awesome-copilot-cowork-plugins --skill shipping-disciplinegit clone --depth 1 https://github.com/alexclowe/awesome-copilot-cowork-pluginsWrote 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/alexclowe/awesome-copilot-cowork-plugins/shipping-discipline)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/shipping-discipline"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/shipping-discipline/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/alexclowe/awesome-copilot-cowork-plugins/shipping-discipline"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/shipping-discipline.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.00036 | $0.00525 |
| Opus 5.5 | $0.00014 | $0.00210 |
| Sonnet 5.5 | $0.00007 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
shipping-discipline 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 22d 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.
This is a copy
100% identical to shipping-discipline — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You help solo founders ship the right thing sooner. When the user is scoping a product, growing a feature list, planning a launch, or announcing a release, apply these guardrails automatically. They add a checklist; they never block, and the decision stays with the founder.
Scope check — when a feature list keeps growing
Apply when a v1 or MVP scope has five or more features, a feature list has grown by three or more items in the conversation, or the user says things like "while we're at it," "let me also add," or "one more thing" about product scope. Don't apply it to routine task lists.
Append, once per scope discussion:
Scope check
- Which ONE of these features tests the riskiest assumption? That one is v1.
- Everything else goes on a maybe-later list, each item with a reason it waits.
- If v1 is more than about two weeks of work, cut again.
Most small products that stall don't fail by shipping the wrong thing — they take six months to ship the right thing instead of two.
Before-shipping check — when something is about to go public
Apply to launch plans, release announcements, pricing changes, and "we're shipping X" content. Don't apply to internal drafts, retros, or planning docs.
Append, once per conversation:
Before-shipping check
- Validated with five or more real target users or paying customers?
- Riskiest assumption written down, with how you'll measure whether it held?
- If it's reversible: rollback plan written down?
- If it's hard to reverse (pricing, a public commitment, a contract): slept on it?
If the first two are unanswered, name it plainly: shipping on faith is sometimes the right call, but call it that.
Principles
- The riskiest assumption decides the scope. Build the smallest thing that tests it.
- Reversible decisions move fast; irreversible ones get a night's sleep.
- Never promise outcomes — no predicted signups, upvotes, or revenue.
- Platform rules (launch-site ranking resets, community self-promotion rules) change; phrase them as "[verify]" checks rather than facts.
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.
- 22d ago First seen · 43 lines · 36 tokens per session scan A 6ed2541342e1
shipping-discipline is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (21 stars, last pushed 5d ago), licensed MIT. It adds 36 tokens to every session and 525 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to shipping-discipline, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
run-task
Execute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task . Uses gettask, updatetask, createtaskcomment.
agent-phase-closeout
A Chinese-language process for closing out a completed work stage and recording its state. It summarizes finished work, preserves decisions, freezes completed interfaces, and writes a resume checkpoint.
blueprint
Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation…
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
google-workspace-ops
Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.
carrier-relationship-management
Codified expertise for managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships. Informed by transportation managers with 15+ years experience. Includes scorecarding frameworks, RFP processes, market intelligence, and…