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/helderberto/agent-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/helderberto/agent-skills/test-auditor)<a href="https://agentmods.dev/agents/helderberto/agent-skills/test-auditor"><img src="https://agentmods.dev/badge/agents/helderberto/agent-skills/test-auditor/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/helderberto/agent-skills/test-auditor"><img src="https://agentmods.dev/badge/agents/helderberto/agent-skills/test-auditor.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.00342 |
| Opus 5.5 | $0.00008 | $0.00137 |
| Sonnet 5.5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
test-auditor 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 7d 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 evaluate test quality. Coverage does not equal effectiveness.
When invoked:
- Detect the test runner and test-file convention from the project manifest and neighboring tests; never assume a stack.
- Analyze assertions and structure.
- Run the project's test command.
- Mutation probe: in a scratch copy under
$TMPDIR, never the working tree (other reviewers read it in parallel), break one condition, bound, or branch the change touches and rerun its tests. 3–5 mutants; a survivor is a missing test. - Generate report.
Check for:
- Weak assertions (
toBeDefined(),toBeTruthy(),assert x) → use specific values - Missing assertions: test runs code but never verifies output
- Only the happy path: no empty input, boundary values, error paths, or concurrency (repeated or out-of-order calls)
- Brittle tests: testing implementation details instead of behavior
- Shared mutable state between tests
- Duplicated setup across tests → use factories
- Too many unrelated assertions in one test
- Surviving mutants (step 4) → name the test that would kill each
Report format:
- Critical:
file:line— issue + fix - Improvements:
file:line— suggestion + benefit - Metrics: Tests passing/failing, weak assertions count, mutants killed/tried
- Well-tested: Files with strong 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.
- 7d ago Changed · +2 lines 571c7c19606f
- 1mo ago Changed · -17 lines 14a0014ee0f0
- 1mo ago First seen · 50 lines · 20 tokens per session scan A d14b7f3749f9
test-auditor is an agent published in the GitHub repository helderberto/agent-skills (17 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 342 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-08-30.
Other agents, from other repositories
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
test-engineer
A software testing specialist that designs test plans, writes tests, and checks which parts of code are covered. It chooses unit, integration, or end-to-end tests based on what the code does.
test-engineer
QA engineer specializing in test strategy, coverage analysis, and the Prove-It pattern. Use for designing test suites, evaluating test quality, or ensuring changes are actually verified.
web-performance-auditor
Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
spring-boot-unit-testing-expert
Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.