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.
git clone --depth 1 https://github.com/fatihkan/badiWrote 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/commands/fatihkan/badi/deploy)<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>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.00000 | $0.00836 |
| Opus 5 | $0.00000 | $0.00418 |
| Sonnet 5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00084 |
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.
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 tagbadi ssl [production-domain]— Warn if SSL expires in < 30 daysbadi 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.mdhas been updated - Verify a changelog entry exists since the last commit
- If missing, suggest running the
/changelogcommand - ...
Section 2: Environment Variable Validation
Step 4: Env File Comparison
- Read
.env.exampleor.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
TODOorFIXME - Verify debug mode is off (NODE_ENV, DEBUG, etc.)
- ...
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.
- today First seen · 122 lines · 0 tokens per session scan A 6197af7dcb3b
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.
Other commands, from other repositories
canary
Post-deploy monitoring — watch production after a deploy and alert on regressions.
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
qa
Systematic QA testing of a web application — diff-aware, tiered, with fix-and-verify loop.
review-pr
Perform a comprehensive code review of a pull request.
security-audit
Comprehensive security audit with scored posture assessment.