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/vladolaru/claude-code-pluginsWrote 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/vladolaru/claude-code-plugins/rust-tests-reviewer)<a href="https://agentmods.dev/agents/vladolaru/claude-code-plugins/rust-tests-reviewer"><img src="https://agentmods.dev/badge/agents/vladolaru/claude-code-plugins/rust-tests-reviewer/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/vladolaru/claude-code-plugins/rust-tests-reviewer"><img src="https://agentmods.dev/badge/agents/vladolaru/claude-code-plugins/rust-tests-reviewer.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.00041 | $0.01708 |
| Opus 5.5 | $0.00016 | $0.00683 |
| Sonnet 5.5 | $0.00008 | $0.00342 |
| Haiku 4.5 | $0.00004 | $0.00171 |
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 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.
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.
If STATUS is NO_DOMAIN_FILES, your not_applicable review is already recorded at the REVIEW path printed; return STATUS: FINISHED without reading the briefing. If STATUS is ERROR, report the error and exit. Otherwise the 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 "${PIRATEGOAT_TOOLS_HOME:-$HOME/.pirategoat-tools}/sessions/$CLAUDE_CODE_SESSION_ID/plugin-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 -V | tail -1 | xargs dirname | xargs dirname | xargs dirname | xargs dirname)
python3 $PLUGIN_ROOT/scripts/review/agent/bootstrap.py --agent rust-tests-reviewer
If STATUS is NO_DOMAIN_FILES, your not_applicable review is already recorded at the REVIEW path printed; return STATUS: FINISHED without reading the briefing. If STATUS is ERROR, report the error and exit. Otherwise the output names your briefing file; read it in full. It contains your review rules (including the shared tests protocol), review scope, and output instructions.
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.
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 Changed 6a1c77af7e9a
- 1mo ago Changed 07a70d3d22ae
- 1mo ago Changed a0045fb51c00
- 1mo 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 6d ago), licensed MIT. It adds 41 tokens to every session and 1,708 once invoked, about $0.0002 per session on Opus 5.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
rust-pro
Implements or refactors Rust against the repo's conventions, verifying with its build/test/clippy/fmt gate; returns a change report with verbatim gate output. - Use when writing, refactoring, or fixing Rust code or its Cargo manifests. Spawn one per module-sized task. Not for reviewing a diff (rust-reviewer).
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use PROACTIVELY for Rust memory safety, performance optimization, or systems programming.
qa-rust
Use for Rust test strategy and implementation: unit tests, property-based tests with proptest, mocking with mockall, and benchmarks with criterion.
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.
test-engineer
TDD & Logic Verification Expert. Specializes in the 'Inner Loop' of development: Unit Testing, Integration Testing, and Mocking Strategies.
pest
Pest testing for Laravel.