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/env-check)<a href="https://agentmods.dev/commands/fatihkan/badi/env-check"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/env-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.00000 | $0.00416 |
| Opus 5 | $0.00000 | $0.00208 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
env-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 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.
What it actually says
.env file validation. Detects missing, extra, empty, and placeholder values + .gitignore check.
Required Tools
- Bash (badi dev env-check)
Procedure
Step 1: Check
badi dev env-check
Reference file detection: .env.example, .env.template, .env.sample
Step 2: Findings
Missing (CRITICAL):
- In .env.example, not in .env
- The user must add it
Extra (WARNING):
- In .env, not in .env.example
- Documentation gap — add to .env.example
Empty value (WARNING):
- The
KEY=orKEY=""form - Fill in the value
Placeholder (CRITICAL):
your_api_key,xxx,changeme,todo,<...>- Not updated with real values
gitignore (CRITICAL):
- If .env is not in .gitignore, add it URGENTLY
Step 3: Common Pattern
# .env.example (committed, with placeholders)
DATABASE_URL=postgresql://user:password@localhost/dbname
API_KEY=your_api_key_here
NODE_ENV=development
# .env (not committed, with real values)
DATABASE_URL=postgresql://prod_user:[email protected]/prod_db
API_KEY=sk-abc123...
NODE_ENV=production
Step 4: Automation
Pre-commit hook:
#!/bin/sh
badi dev env-check || exit 1
CI pipeline:
- name: Validate .env
run: badi dev env-check
Step 5: Combine with the Secret Scanner
Comprehensive security:
badi dev env-check # .env validation
badi secret-scan # in-code secret scan
Example
/env-check
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 · 77 lines · 0 tokens per session scan A 265cb4dd8def
env-check 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 416 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
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
investigate
Systematic root-cause debugging — find the cause before writing any fix.
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.
git-worktree-clean
Clean up stale git worktrees with merged branch detection and disk usage report.