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 mikestangdevs/craft-skills --skill readiness-gategit clone --depth 1 https://github.com/mikestangdevs/craft-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/mikestangdevs/craft-skills/readiness-gate)<a href="https://agentmods.dev/skills/mikestangdevs/craft-skills/readiness-gate"><img src="https://agentmods.dev/badge/skills/mikestangdevs/craft-skills/readiness-gate/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/mikestangdevs/craft-skills/readiness-gate"><img src="https://agentmods.dev/badge/skills/mikestangdevs/craft-skills/readiness-gate.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.00156 | $0.01230 |
| Opus 5 | $0.00078 | $0.00615 |
| Sonnet 5 | $0.00031 | $0.00246 |
| Haiku 4.5 | $0.00016 | $0.00123 |
Grade A, and why
readiness-gate 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 9d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Readiness Gate
The failure mode this fixes
"Done. Should work now." — the most expensive sentence in agent-assisted engineering. The user ships, demos, or builds on top of it, and discovers in production what "should" was hiding. When they come back burned, the trust loss costs more than the bug: now every future "done" gets re-verified by hand, and the agent's leverage collapses.
The root defect is uncalibrated confidence. Agents report completion as a mood ("everything looks good!") rather than a claim with evidence. They answer "are you sure?" with escalating enthusiasm instead of escalating proof. And under pressure to be concise, they truncate exactly the part that matters — the caveats, the unverified paths, the one failing edge they decided was probably fine.
A readiness gate makes "done" a structured claim: verified / not verified / changed / residual risk / go or no-go. It's allowed to say no-go. It's required to say what it doesn't know.
When to Use This Skill
- Finishing any unit of work, before reporting it complete
- Before a ship, demo, deploy, or handoff — anything with an audience or a blast radius
- The user asks "are we ready?", "are you sure?", "so everything works?"
- Checking deliverables against a spec, checklist, or requirements doc
- You notice the words "should", "probably", or "looks good" forming in a completion report
Don't use when: mid-task on intermediate steps (gates are for boundaries, not every commit), or for trivial changes where the full ceremony outweighs the risk — but even a one-line fix gets one honest sentence of what was and wasn't verified.
Instructions
1. Separate what you verified from what you believe
For every claim in the report, ask: did I watch this work, or do I expect it to work? Verified means executed and observed — a test run, a live request, a rendered page, a queried row. Everything else is belief, and belief gets labeled as such. "The migration ran clean (verified, 4 rows updated); rollback path is implemented but untested (belief)."
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.
- 9d ago First seen · 73 lines · 156 tokens per session scan A 642e5be2028b
readiness-gate is a skill published in the GitHub repository mikestangdevs/craft-skills (4 stars, last pushed 3mo ago), licensed MIT. It adds 156 tokens to every session and 1,230 once invoked, about $0.0008 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-31.
Other skills, from other repositories
absolute-simplify
Use when the user wants to simplify, clean up, refactor, tidy, or refine code — their staged/unstaged git changes or a target file/path. Reduces complexity, flattens nesting, removes redundancy and dead code, scores each change by value (holding low-value churn), then runs tests to prove nothing broke. Invoke on…
plumb-line-audit
Use when auditing a diff or repository against the plumb-line principles — finds laundered uncertainty, boundary leaks, hardcoded priors, overstated maturity, outputs lacking recorded lineage, and baseline drift with no explanation. Read-only: it reports, never auto-fixes.
plumb-line-bootstrap
Use when setting up a project with the plumb-line discipline — interviews the builder to find their source-truth layer and layering, generates a domain-neutral ruleset, and installs parameterized enforcement (boundary check, test gate, pre-commit gate, branch guard) for the project's language. Ships no default layers…
plumb-line-remediate
Use when applying findings from a plumb-line audit report — the builder has a report (or pasted findings) and wants the fixes made. Opt-in and separate from the audit, which is read-only and never fixes.
plumb-line-adopt
Use when a builder wonders what plumb-line would do for their codebase or which part to adopt — or when, mid-task, their work shows a fit signal (adding a mock or fallback near a production path, mixing fixture, cached, or LLM/agent-produced data with real data) and visible uncertainty would help. Inspects the repo…
plumb-line-method
Use when a builder wants to learn or be reminded of the plumb-line method — the discipline of epistemic honesty enforced by tooling. Teaches the thesis, the nine portable principles, the maturity vocabulary, and the one-line test. Pure knowledge; takes no actions.