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/pedrol-cmd/brain-drinWrote 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/pedrol-cmd/brain-drin/test-gen)<a href="https://agentmods.dev/commands/pedrol-cmd/brain-drin/test-gen"><img src="https://agentmods.dev/badge/commands/pedrol-cmd/brain-drin/test-gen/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/pedrol-cmd/brain-drin/test-gen"><img src="https://agentmods.dev/badge/commands/pedrol-cmd/brain-drin/test-gen.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.00019 | $0.00307 |
| Opus 5.5 | $0.00008 | $0.00123 |
| Sonnet 5.5 | $0.00004 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
test-gen 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
Test Generation
Context
- Target: $ARGUMENTS
- Test framework: detect from package.json, pytest.ini, or existing test files
- Existing tests: !
find . -name "*test*" -o -name "*spec*" | head -20 2>/dev/null
Your Task
- Read the target code thoroughly
- Identify what to test:
- Happy path (normal operation)
- Edge cases (null, empty, boundary, max values)
- Error paths (invalid input, network failures, timeouts)
- Integration points (DB, APIs, external services)
- Generate complete, runnable test file
- Run the tests and fix any failures
Test Quality
- One logical assertion per test
- Clear test names:
should [behavior] when [condition] - Arrange-Act-Assert structure
- No shared mutable state between tests
- Real implementations over mocks when feasible
- Fast: unit <100ms, integration <5s
Rules
- Match existing test patterns and conventions in the project
- Don't test framework behavior or trivial code
- Every test must be able to fail (if it can never fail, it's useless)
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 · 39 lines · 19 tokens per session scan A 4261df9d234a
test-gen is a command published in the GitHub repository pedrol-cmd/brain-drin (12 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 307 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
gsd:add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
test
Escrever e rodar testes (skill 05 — QA Engineer).
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
test
Load the testing strategies skill for 3-tier testing with NO MOCKING policy enforcement in Tier 2-3.
verify
You are invoking the verify skill - comprehensive verification following Boris Cherny's pattern.