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 faizkhairi/claude-code-blueprint --skill deploy-checkgit clone --depth 1 https://github.com/faizkhairi/claude-code-blueprintWrote 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/faizkhairi/claude-code-blueprint/deploy-check)<a href="https://agentmods.dev/skills/faizkhairi/claude-code-blueprint/deploy-check"><img src="https://agentmods.dev/badge/skills/faizkhairi/claude-code-blueprint/deploy-check.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.00167 | $0.00629 |
| Opus 5 | $0.00084 | $0.00315 |
| Sonnet 5 | $0.00033 | $0.00126 |
| Haiku 4.5 | $0.00017 | $0.00063 |
Grade A, and why
deploy-check 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 7d 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.
What it actually says
Pre-deployment validation for $ARGUMENTS environment:
- Tests: Run full test suite, all must pass
- Git status: Check for uncommitted changes across all repos
- Schema sync: Verify the project's ORM/DB schema definition matches expectations (e.g. Prisma schema, Django models, Rails schema.rb, migrations directory)
- Secrets check: Scan for hardcoded credentials, API keys, passwords
- Dev artifacts: Check for language-appropriate debug/print statements (console.log, print(), System.out.println, fmt.Println, etc.), debugger statements, TODO/FIXME in production paths
- Env vars: Verify required environment variables are documented
- Auth coverage: Validate all API endpoints have auth middleware
- Dependency audit: Run the ecosystem's dependency audit (
npm audit/yarn audit,pip-audit,bundle audit,cargo audit,govulncheck, etc., detected from the manifest/lockfile). Classify: CRITICAL/HIGH (action required) vs MODERATE/LOW (note). Separate production vs dev-only vulnerabilities. Check for auto-fixable with--dry-run. - Build: Verify project builds without errors
- Migration safety: Check if any ORM models/migrations are missing (risk of tables dropped by destructive sync)
If argument is "audit" → run only step 8 (dependency vulnerability scan) across the current project.
GO/NO-GO Criteria
- NO-GO: Any test failure, hardcoded secret found, ORM model/migration missing, build failure, or CRITICAL/HIGH vulnerability in production deps
- GO: All steps pass. MODERATE/LOW vulnerabilities in dev-only deps are acceptable with note.
- GO with warnings: All critical steps pass but non-blocking issues exist (dev-only vulns, TODO items in non-critical paths)
Output: GO / NO-GO status with detailed checklist results.
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.
- 7d ago First seen · 29 lines · 167 tokens per session scan A 8cc3858427ce
deploy-check is a skill published in the GitHub repository faizkhairi/claude-code-blueprint (70 stars, last pushed 25d ago), licensed MIT. It adds 167 tokens to every session and 629 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-30.
Other skills, from other repositories
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
ijfw-ship
Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…
ijfw-preflight
Run the IJFW preflight pipeline (11 gates, fail-fast). Trigger: 'ijfw preflight', 'run preflight', 'check before ship', 'preflight gates', 'validate before release'.
upload
Pre-upload gate for track handoff. Verifies review status, HLD approvals, deploy checklist, and validator chain before git upload or PR submission.
release-verification
A release-verification checklist for software versions and packages. It covers changelogs, tests, packaging, installation smoke checks, version-control actions, publishing, and checks after release.
audit-release
A pre-release review assistant that checks whether a software package or plugin is ready to publish.