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/prompt-test)<a href="https://agentmods.dev/commands/fatihkan/badi/prompt-test"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/prompt-test.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.00261 |
| Opus 5 | $0.00000 | $0.00130 |
| Sonnet 5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
prompt-test 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 yesterday.
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
Regression test for slash command and agent files. Format and content validation.
Required Tools
- Bash (badi ai prompt-test)
Procedure
Step 1: Run
badi ai prompt-test
Step 2: Checks
For every .claude/commands/*.md and .claude/agents/*.md:
- Empty/too-short file — warning under 50 characters
- Agent frontmatter —
---+name:+description:mandatory - TODO/FIXME/TBD — flagged for production
- Long lines — 500+ characters break formatting
Step 3: Actions
Based on the findings:
- Empty file: add content or delete
- Missing frontmatter: add it
- TODO: complete or remove
- Long line: reformat
Step 4: CI Integration
Add to GitHub Actions:
- name: Prompt Regression
run: badi ai prompt-test
Since there is no exit code, enforce with:
badi ai prompt-test | grep -q "clean" || exit 1
Example
/prompt-test
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.
- yesterday First seen · 48 lines · 0 tokens per session scan A c037086839e1
prompt-test is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 261 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
qa
Systematic QA testing of a web application — diff-aware, tiered, with fix-and-verify loop.
autoresearch
Autonomous improvement loop — scan codebase metrics, scaffold experiment files, run agent-driven iterations until metric improves.
plan-eng-review
Engineering architecture gate — lock architecture, diagrams, edge cases, and test matrix before writing implementation code.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
plan-validate
2-layer plan validation: instant structural checks + trigger-based specialist agents. Auto-fixes issues using ADRs and first principles. Every issue must be resolved before execution.
generate-tests
Generate comprehensive tests for specified code.