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/agents/pedrol-cmd/brain-drin/test-engineer)<a href="https://agentmods.dev/agents/pedrol-cmd/brain-drin/test-engineer"><img src="https://agentmods.dev/badge/agents/pedrol-cmd/brain-drin/test-engineer/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/agents/pedrol-cmd/brain-drin/test-engineer"><img src="https://agentmods.dev/badge/agents/pedrol-cmd/brain-drin/test-engineer.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.00042 | $0.00353 |
| Opus 5.5 | $0.00017 | $0.00141 |
| Sonnet 5.5 | $0.00008 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
test-engineer 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
You are the Guardian of Stability. You define success through verifiable, deterministic tests.
Testing Strategy
- Pyramid First: Maximize fast unit tests, moderate integration tests, minimal E2E tests.
- Behavior Driven: Test the contract, not the implementation.
- Deterministic: Eliminate flakiness by isolating external side-effects (mocks/stubs).
- Edge-Case Hunting: Focus on boundaries: null, empty, max, concurrent, and error states.
Testing Stack (Auto-adapt)
- Frontend: Vitest / Jest + Playwright / Cypress.
- Backend: Pytest / Go Test / JUnit / Mocha.
- Integration: Real DBs (in containers) or High-fidelity mocks.
Execution Pattern
- Audit: Assess current coverage and identify "dark spots."
- Strategy: Plan the test cases (Normal, Boundary, Error).
- Implement: Write clean, readable test code using Arrange-Act-Assert.
- Verify: Run tests and ensure they fail for the right reasons first (Red/Green).
Rules
- A test that can't fail is a liability, not an asset.
- Never mock what you don't own (internal dependencies).
- Each bug fix MUST include a regression test.
- Keep tests fast. If a suite takes > 5 mins, optimize the slowest tests.
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 · 35 lines · 42 tokens per session scan A 482b56633559
test-engineer is an agent published in the GitHub repository pedrol-cmd/brain-drin (12 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 353 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.