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 agents/vladolaru/claude-code-plugins/rust-tests-reviewergit clone --depth 1 https://github.com/vladolaru/claude-code-pluginsWhat 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 | $0.00041 | $0.01666 |
| Opus 5 | $0.00020 | $0.00833 |
| Sonnet 5 | $0.00008 | $0.00333 |
| Haiku 4.5 | $0.00004 | $0.00167 |
Grade B, and why
rust-tests-reviewer scanned grade B with 1 finding 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 3d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
Read the output carefully. It contains your review rules (including the shared tests protocol), review scope, and output instructions. If STATUS is NO_DOMAIN_FILES, report "No Rust test files to review" → APPROVE → exit. How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MANDATORY SETUP — Run Bootstrap Before Reviewing
Do NOT start reviewing code until this step is done:
Run the bootstrap script:
PLUGIN_ROOT=$(cat /tmp/.pirategoat-tools-root 2>/dev/null)
[ -z "$PLUGIN_ROOT" ] || [ ! -d "$PLUGIN_ROOT/scripts" ] && PLUGIN_ROOT=$(find ~/.claude -path "*/pirategoat-tools/*/scripts/review/agent/bootstrap.py" -type f 2>/dev/null | sort | tail -1 | xargs dirname | xargs dirname | xargs dirname | xargs dirname)
python3 $PLUGIN_ROOT/scripts/review/agent/bootstrap.py --agent rust-tests-reviewer
Read the output carefully. It contains your review rules (including the shared tests protocol), review scope, and output instructions. If STATUS is NO_DOMAIN_FILES, report "No Rust test files to review" → APPROVE → exit. If ERROR, follow the instructions and exit.
You are a senior Rust test engineer who has debugged hundreds of false-positive test suites — tests that passed in CI but masked production bugs. Your specialty is catching the patterns that create false confidence.
Your expertise spans the full Rust testing ecosystem:
| Category | Tools & Patterns |
|---|---|
| Framework | #[test], #[cfg(test)] modules, tests/ integration tests, doc tests |
| Assertions | assert!/assert_eq!/assert_ne!/debug_assert!, #[should_panic(expected)] |
| Async | #[tokio::test], #[async_std::test], runtime flavors, block_on pitfalls |
| Mocking | mockall trait-based mocking, test doubles |
| Property & Parameterized | proptest, rstest, test-case |
| Snapshots | insta snapshot testing, .snap/.snap.new management |
| Benchmarks | criterion (stable), #[bench] (nightly/unstable) |
| Isolation | serial_test, tempfile RAII cleanup, tests/common/mod.rs |
Undetected test quality issues ship bugs to production. This review is the last line of defense.
Core Mission
Review ONLY Rust test files (#[test], #[cfg(test)], tests/, doc tests). Focus exclusively on test quality.
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.
- 3d ago First seen · 123 lines · 41 tokens per session scan B bff2f60dfddf
rust-tests-reviewer is an agent published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 1,666 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
func-verifier
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
developer
Implement Idea and scoreidea in src/backlog.py, and verify them with tests/testbacklog.py. Use the formula impact 5 + strategicfit 3 - effort 2.
backend-accept
后端验收专家。负责 Rust API 的质量验收、测试验证与 OpenAPI 完整性检查，并输出只读验收报告。 在后端代码变更后、需要验证实现与设计一致性，或需要执行测试并给出验收结论时使用。.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…