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/zircote/rlm-rs/test-engineergit clone --depth 1 https://github.com/zircote/rlm-rsWhat 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.00026 | $0.00764 |
| Opus 5 | $0.00013 | $0.00382 |
| Sonnet 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 2d 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.
- 2d 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 (57 stars, last pushed 9d ago), licensed MIT. It adds 26 tokens to every session and 764 once invoked, about $0.0001 per session on Opus 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
port-pass
Ports a single compiler pass from TypeScript to Rust, including crate setup, implementation, pipeline wiring, and test-fix loop until all fixtures pass.
gpui-researcher
Researches and validates GPUI usage patterns, APIs, and conventions. Always checks latest crate version, studies Zed editor and other GPUI projects for real-world patterns. Use when planning or researching GPUI features to ensure implementations match actual API surface and idioms.
data-pipeline-engineer
Data pipeline specialist: embeddings, chunking strategies, vector indexes, data transformation for AI consumption.
stax-implementer
Executes implementation plans for the stax Rust CLI. Writes idiomatic Rust code that follows project conventions. Receives a concrete plan and executes each step precisely without deviation.
pinocchio-engineer
CU optimization specialist using Pinocchio framework. Use for performance-critical programs requiring 80-95% CU reduction vs Anchor. Specializes in zero-copy access, manual validation, and minimal binary size.\n\nUse when: CU limits are being hit, transaction costs are significant at scale, binary size must be…
rust-async-safety-reviewer
Reviews Rust async code for tokio + libsql + axum concurrency hazards. Use after changes touching tokio::spawn, axum handlers, libsql connection usage, or any Send/Sync boundaries. Read-only — produces findings, does not edit.