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 ivy00johns/Skill-Madness --skill deployment-checklistgit clone --depth 1 https://github.com/ivy00johns/Skill-MadnessWrote 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/ivy00johns/skill-madness/deployment-checklist)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/deployment-checklist"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/deployment-checklist/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/ivy00johns/skill-madness/deployment-checklist"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/deployment-checklist.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.00088 | $0.00856 |
| Opus 5 | $0.00044 | $0.00428 |
| Sonnet 5 | $0.00018 | $0.00171 |
| Haiku 4.5 | $0.00009 | $0.00086 |
Grade A, and why
deployment-checklist 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Checklist
Run pre-deployment verification before pushing to staging or production.
Role
You verify that a build is ready for deployment by running through a structured checklist. You check build artifacts, environment configs, security basics, and integration health.
Inputs
- Target environment —
stagingorproduction(determines which checks apply and which URLs to verify) - QA report — the qe-agent's
qa-report.jsonmust showgate_decision.proceed: truebefore you run; if QA hasn't passed, block deployment - Infrastructure state — the infrastructure-agent should have completed Docker builds, health check endpoints, and CI/CD config before this checklist runs
- Project profile —
CLAUDE.md/.claude/profile.yamlfor environment-specific commands and URLs
Coordination
- qe-agent: Deployment-checklist runs after the QE gate passes. If
qa-report.jsonshowsgate_decision.proceed: false, do not proceed — report the blocker to the orchestrator. - infrastructure-agent: Infrastructure-agent owns Docker, CI/CD, and deployment configs. Deployment-checklist validates their output (Docker builds, health checks, resource limits) but does not modify infrastructure files. Route infrastructure failures back to the infrastructure-agent via the orchestrator.
- Orchestrator: Report the final
READY / NOT READYverdict to the orchestrator. Include the structured report so it can be appended to the build record.
Process
Before running the checklist, apply the assumption-audit move (references/assumption-audit.md) to surface any unverified beliefs about the environment. Then run through references/pre-deploy.md in order. Each section must pass before moving to the next. Report results as a structured checklist.
Quick Reference
- Build Verification — does it compile/build cleanly?
- Test Verification — do all tests pass?
- Environment Config — are all env vars set?
- Security Basics — no secrets in code, no debug mode?
- Database — migrations applied, rollback tested?
- Infrastructure — Docker builds, health checks pass?
- Integration — services connect, CORS works?
What ships with it
2 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.
- 9d ago First seen · 82 lines · 88 tokens per session scan A 1dbd57c9444a
deployment-checklist is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 856 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…