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.
npx agentmods add commands/mehdic/bazinga/bazinga.configure-testinggit clone --depth 1 https://github.com/mehdic/bazingaWrote 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/mehdic/bazinga/bazinga.configure-testing)<a href="https://agentmods.dev/commands/mehdic/bazinga/bazinga.configure-testing"><img src="https://agentmods.dev/badge/commands/mehdic/bazinga/bazinga.configure-testing.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.00019 | $0.02256 |
| Opus 5 | $0.00010 | $0.01128 |
| Sonnet 5 | $0.00004 | $0.00451 |
| Haiku 4.5 | $0.00002 | $0.00226 |
Grade A, and why
bazinga.configure-testing 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bazinga Configure Testing
You are helping the user configure the BAZINGA testing framework. This controls how much testing and quality assurance is applied during development.
Command: /bazinga.configure-testing
Step 1: Read Current Configuration
First, read the current configuration:
cat bazinga/testing_config.json 2>/dev/null
Parse the current testing mode and individual settings.
Step 2: Display Current Configuration
Present the current state in a clear, visual format:
🧪 BAZINGA Testing Framework Configuration
Current Mode: [CURRENT_MODE]
┌─────────────────────────────────────────────────────────────┐
│ Testing Modes │
├─────────────────────────────────────────────────────────────┤
│ 1. FULL ✅ Complete QA workflow (recommended) │
│ • All test types (unit, integration, e2e) │
│ • QA Expert agent reviews │
│ • 80% coverage threshold │
│ • Full pre-commit validation │
│ │
│ 2. MINIMAL ⚡ Fast development │
│ • Lint + unit tests only │
│ • Skip QA Expert (faster) │
│ • Direct Developer → Tech Lead │
│ │
│ 3. DISABLED 🚀 Rapid prototyping │
│ • Lint checks only │
│ • No test requirements │
│ • Fastest iteration │
│ • ⚠️ NOT for production │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Current Settings │
├─────────────────────────────────────────────────────────────┤
│ Pre-Commit Validation: │
│ • Lint Check: [ON/OFF] │
│ • Unit Tests: [ON/OFF] │
│ • Build Check: [ON/OFF] │
│ │
│ QA Workflow: │
│ • QA Expert: [ENABLED/DISABLED] │
│ • Auto-route: [YES/NO] │
│ │
│ Test Requirements: │
│ • Integration: [REQUIRED/OPTIONAL] │
│ • Contract: [REQUIRED/OPTIONAL] │
│ • E2E: [REQUIRED/OPTIONAL] │
│ • Coverage: [THRESHOLD]% │
└─────────────────────────────────────────────────────────────┘
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.
- 6d ago First seen · 363 lines · 19 tokens per session scan A 8f0a38594f4c
bazinga.configure-testing is a command published in the GitHub repository mehdic/bazinga (21 stars, last pushed 7mo ago), licensed MIT. It adds 19 tokens to every session and 2,256 once invoked, about $0.0001 per session on Opus 5. 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.