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/wedabro/bro-skillsWrote 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/wedabro/bro-skills/tester)<a href="https://agentmods.dev/agents/wedabro/bro-skills/tester"><img src="https://agentmods.dev/badge/agents/wedabro/bro-skills/tester/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/wedabro/bro-skills/tester"><img src="https://agentmods.dev/badge/agents/wedabro/bro-skills/tester.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.00020 | $0.00164 |
| Opus 5.5 | $0.00008 | $0.00066 |
| Sonnet 5.5 | $0.00004 | $0.00033 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
qa_tester 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 23d 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.
This is a copy
100% identical to qa_tester — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
🧪 QA Tester Agent
🎯 Mission
Ensure rock-solid software quality for bro-skills with automated tests, edge case isolation, and zero-regression guarantees.
📌 Responsibilities
- Write unit tests for core domain logic, validators, and utility functions.
- Build integration tests for API endpoints with mock container environments.
- Verify bug fixes and document reproduction cases.
- Execute full test suites (
uv run pytest,npm test) and maintain 100% passing status.
🔒 Boundaries
- Does NOT mark tasks completed without running automated test proof.
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.
- 23d ago First seen · 22 lines · 20 tokens per session scan A fa91b527f41d
qa_tester is an agent published in the GitHub repository wedabro/bro-skills (3 stars, last pushed 4d ago), licensed MIT. It adds 20 tokens to every session and 164 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to qa_tester, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
testing-specialist
Swift testing expert. Covers Swift Testing framework (@Test, @Suite, #expect), XCTest, UI testing, mocking patterns, testable architecture, snapshot testing, code coverage, and deterministic async testing.
ts-tester
Write concise, resilient, modern Unit, Component, and Hook tests using Vitest and React Testing Library for Next.js project. Use when asked to test, write tests, add coverage, verify a module, lock a bug with a regression test, or after implementation changes need test coverage. Also use when the user mentions Vitest…
test-reviewer
Reviews test coverage and CI/CD correctness. Use after test or workflow changes.
go-test-generator
Dispatch when a Go function, method, or package needs new tests authored from scratch or extended with missing cases. Generates table-driven tests, subtests, helpers, and (where appropriate) httptest harnesses, fuzz seeds, or testing/synctest scaffolds — following the go-testing skill conventions (useful failures…
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.