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 giang6283623/minimal-vibe-coding-kit --skill clean-deliverygit clone --depth 1 https://github.com/giang6283623/minimal-vibe-coding-kitWrote 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/giang6283623/minimal-vibe-coding-kit/clean-delivery)<a href="https://agentmods.dev/skills/giang6283623/minimal-vibe-coding-kit/clean-delivery"><img src="https://agentmods.dev/badge/skills/giang6283623/minimal-vibe-coding-kit/clean-delivery.svg" alt="Measured on agentmods" 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.00057 | $0.00933 |
| Opus 5 | $0.00028 | $0.00466 |
| Sonnet 5 | $0.00011 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
clean-delivery 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 8d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Delivery
Deliver one small, observable behavior slice with evidence. The six stages are quality gates, not six mandatory agents.
Before work
Read these files completely:
- references/story-template.md
- references/verification-tiers.md
- references/architecture-contract.md
- references/proof-return-mapping.md
Read backbone.yml and repository instructions. Refuse protected-path changes without approval. Never install tools, enable hooks, or broaden authority merely to satisfy a gate.
Required input contract
Freeze one story before implementation. Record:
- one observable behavior;
- in-scope and out-of-scope work;
- editable paths and protected verifier assets;
- acceptance criteria;
- the expected failing check and proof commands;
- a low, medium, high, or critical risk tier.
Create the story from references/story-template.md, then validate it:
node .vibekit/skills/clean-delivery/scripts/validate-story.mjs <story.md>
A missing verifier is a declared proof gap, not permission to invent evidence. "not-configured: " is valid only when the gate is not proportionate to the slice.
Six gates
1. Specify
Turn the request into one story whose outcome can be observed from outside the implementation. Resolve material ambiguity before code. Keep Gherkin optional: clear bullet criteria are acceptable.
Exit when the story validator passes and scope is frozen.
2. Code
Run the smallest relevant check before implementation and capture the expected failure. Implement only enough production code to make the behavior pass. Do not weaken tests or protected verifier assets.
For a documentation-only or configuration-only slice, record why a red unit test is not applicable and use the smallest deterministic validator that can fail before the change.
Exit when the red evidence is authentic and the minimal behavior passes.
3. Clean
Improve names, duplication, function size, and error clarity without changing behavior. Prefer domain language and single-purpose units. Rerun the same focused proof after each meaningful cleanup.
What ships with it
6 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.
- 8d ago First seen · 99 lines · 57 tokens per session scan A 8f1b2c5aacaa
clean-delivery is a skill published in the GitHub repository giang6283623/minimal-vibe-coding-kit (21 stars, last pushed 10d ago), licensed MIT. It adds 57 tokens to every session and 933 once invoked, about $0.0003 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
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.