deploy

deploy is a command for Claude Code from fatihkan/badi. It costs 0 tokens per session (836 once invoked), scanned A, original, MIT.

A deployment readiness checklist that reviews whether a project is ready to release. It reports findings but does not deploy the project itself.

In plain words
What is it for?
Use it to run pre-release checks, review recent changes, look for leaked secrets, check SSL certificate expiry and DNS health, and compare performance with a baseline.
Why use it?
It brings together checks for tests, secrets, commits, changelogs, certificates, DNS, and performance so problems can be found before release.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Part of the badi plugin — 81 skills, 86 commands, 30 agents, 7 hooks shipped together

Good fit Use it to run pre-release checks, review recent changes, look for leaked secrets, check SSL certificate expiry and DNS health, and compare performance with a baseline.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/fatihkan/badi/deploy
Install

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.

Clone the repo
git clone --depth 1 https://github.com/fatihkan/badi

Made for: Claude Code.

Or install badi, the plugin that ships this one along with the rest of its 81 skills, 86 commands, 30 agents, 7 hooks.

Wrote 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.

agentmods badge for deploy

README.md
[![agentmods](https://agentmods.dev/badge/commands/fatihkan/badi/deploy.svg)](https://agentmods.dev/commands/fatihkan/badi/deploy)
Your own site
<a href="https://agentmods.dev/commands/fatihkan/badi/deploy"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/deploy.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 836 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00836
Opus 5 $0.00000 $0.00418
Sonnet 5 $0.00000 $0.00167
Haiku 4.5 $0.00000 $0.00084

Measured today against content hash 6197af7dcb3b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

deploy 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 today.

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.

.claude/commands/deploy.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deployment checklist. Verifies all pre-deployment requirements and produces a readiness report.

Badi CLI Pre-Deploy Checklist (v1.6+)

ALWAYS run these checks before deploying:

  • badi secret-scan — No secret leakage allowed (CRITICAL — block the deploy on exit 1)
  • badi commit --check — Last commit in conventional format (for changelog generation)
  • badi changelog — Review the changes since the last tag
  • badi ssl [production-domain] — Warn if SSL expires in < 30 days
  • badi dns [domain] — DNS health (email security)
  • badi lighthouse [url] — Performance baseline (for regression detection)

Required Tools

  • Bash (git commands, running tests, env variable checks)
  • Read (configuration files, changelog)
  • Grep (code and configuration scan)
  • ...

Important Note

This command does NOT deploy by itself. It evaluates deployment readiness and leaves the final decision to the user.


Section 1: Pre-Deployment Validation

Step 1: Test Suite Check

  • Run the full test suite (or check the latest CI result)
  • Determine whether any tests fail
  • Report the coverage ratio
  • ...

Step 2: Critical Audit Finding Check

  • Read audit-trail.md (if present)
  • Check for T0 (critical) findings since the last deploy
  • Scan for unresolved security warnings
  • ...

Step 3: Changelog Validation

  • Check whether CHANGELOG.md has been updated
  • Verify a changelog entry exists since the last commit
  • If missing, suggest running the /changelog command
  • ...

Section 2: Environment Variable Validation

Step 4: Env File Comparison

  • Read .env.example or .env.template
  • List the variables that must be defined
  • Detect variables possibly missing in production

Step 5: Sensitive Value Check

Run the Badi Secret Scanner:

badi secret-scan --git    # Working tree + last 100 commits

If the exit code is 1 (critical/high secret found), the deploy MUST BE BLOCKED.

  • Scan for hardcoded environment values in the code
  • Find environment references containing TODO or FIXME
  • Verify debug mode is off (NODE_ENV, DEBUG, etc.)
  • ...

Read the full file on GitHub · 122 lines

Changes

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.

  1. today First seen · 122 lines · 0 tokens per session scan A 6197af7dcb3b

Subscribe to this mod's changes

deploy is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 836 tokens. 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-09-06.