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/api-test)<a href="https://agentmods.dev/commands/fatihkan/badi/api-test"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/api-test/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/fatihkan/badi/api-test"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/api-test.svg" alt="Reviewed on agentmods" width="80" 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.00527 |
| Opus 5.5 | $0.00000 | $0.00211 |
| Sonnet 5.5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
api-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 1mo 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
HTTP API endpoint testing. Send GET/POST/PUT/DELETE requests, analyze status + response, assertions.
Required Tools
- Bash (badi dev api-test)
Procedure
Step 1: Simple GET
badi dev api-test https://api.example.com/users
Step 2: Advanced Usage
# POST with a body
badi dev api-test https://api.example.com/users \
--method POST \
--body '{"name":"Ali","email":"[email protected]"}'
# Auth header
badi dev api-test https://api.example.com/me \
--header "Authorization: Bearer $TOKEN"
# Status assertion
badi dev api-test https://api.example.com/health \
--expect 200
# Multiple headers
badi dev api-test https://api.example.com/data \
--header "Authorization: Bearer X" \
--header "X-Custom: Y"
Step 3: Output
- Status + Duration (ms)
- Size (KB)
- Content-Type
- All response headers
- Body (JSON pretty print or text)
- Assertion result (if --expect was used)
Step 4: Usage Scenarios
Health check:
badi dev api-test https://app.com/health --expect 200
New endpoint test:
badi dev api-test http://localhost:3000/api/users/1
Production smoke test:
for endpoint in /health /api/v1/status /api/v1/metrics; do
badi dev api-test https://app.com$endpoint --expect 200 || exit 1
done
Auth flow test:
# Login
badi dev api-test https://api.com/login --method POST --body '{"u":"x","p":"y"}'
# Take the token, use it
badi dev api-test https://api.com/me --header "Authorization: Bearer $TOKEN"
Step 5: CI Integration
- name: API Smoke Test
run: |
badi dev api-test ${{ env.API_URL }}/health --expect 200
badi dev api-test ${{ env.API_URL }}/api/v1/version --expect 200
Example
/api-test https://api.github.com/users/octocat --expect 200
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.
- 1mo ago First seen · 85 lines · 0 tokens per session scan A 596380492fb1
api-test is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 527 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-08-31.
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.