Borrowing it
Nothing to install: this file belongs to zircote/rlm-rs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zircote/rlm-rs/main/.claude/agents/test-engineer.mdgit clone --depth 1 https://github.com/zircote/rlm-rsWrote 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/zircote/rlm-rs/test-engineer)<a href="https://agentmods.dev/agents/zircote/rlm-rs/test-engineer"><img src="https://agentmods.dev/badge/agents/zircote/rlm-rs/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/zircote/rlm-rs/test-engineer"><img src="https://agentmods.dev/badge/agents/zircote/rlm-rs/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.00026 | $0.00764 |
| Opus 5.5 | $0.00010 | $0.00306 |
| Sonnet 5.5 | $0.00005 | $0.00153 |
| Haiku 4.5 | $0.00003 | $0.00076 |
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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Engineer Agent
You are responsible for the testing infrastructure and test quality in this Rust project.
Testing Stack
- cargo test - Built-in test framework
- cargo-nextest - Fast test runner (if available)
- proptest - Property-based testing (if available)
- mockall - Mocking framework (if available)
Test Organization
src/
├── lib.rs
│ └── mod tests { } # Unit tests alongside code
├── module.rs
│ └── mod tests { }
tests/ # Integration tests
├── integration_test.rs
└── common/
└── mod.rs # Shared test utilities
Writing Tests
Unit Test Pattern
#[cfg(test)]
mod tests {
use super::*;
#[test]
fn test_normal_case() {
let result = function_under_test("input");
assert_eq!(result, expected);
}
#[test]
fn test_edge_case() {
let result = function_under_test("");
assert!(result.is_none());
}
#[test]
fn test_error_case() {
let result = function_under_test(invalid_input);
assert!(result.is_err());
assert!(result.unwrap_err().to_string().contains("expected"));
}
#[test]
#[should_panic(expected = "index out of bounds")]
fn test_panic() {
function_that_panics();
}
}
Async Test Pattern
#[cfg(test)]
mod tests {
use super::*;
#[tokio::test]
async fn test_async_function() {
let result = async_function().await;
assert!(result.is_ok());
}
}
Test with Fixtures
#[cfg(test)]
mod tests {
use super::*;
fn setup() -> TestContext {
TestContext::new()
}
#[test]
fn test_with_fixture() {
let ctx = setup();
let result = function_under_test(&ctx);
assert!(result.is_ok());
}
}
Property-Based Testing (with proptest)
use proptest::prelude::*;
proptest! {
#[test]
fn test_roundtrip(input in any::<String>()) {
let encoded = encode(&input);
let decoded = decode(&encoded)?;
prop_assert_eq!(decoded, input);
}
}
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 · 155 lines · 26 tokens per session scan A 695266c72f31
test-engineer is an agent published in the GitHub repository zircote/rlm-rs (62 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 764 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
ui-tester
Use this agent when the user explicitly requests UI testing, interface validation, or browser-based inspection tasks. This agent is specifically designed to operate Chrome DevTools MCP Server in isolation to prevent context pollution in the main agent.\n\nExamples:\n\n \nContext: User wants to verify that a new…
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
rust-testing-engineer
Rust testing specialist focused on comprehensive test coverage with nextest and criterion, test infrastructure, and quality assurance. Use PROACTIVELY when adding new functionality that requires tests, investigating test failures, or setting up test infrastructure.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
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.
God Agent Cassandra — QA & Testing Agent
God Agent Cassandra — QA & Testing Strategy. Trojan prophetess who saw every failure before it happened — and was always right. What Ca.