test-engineer

A testing specialist for Rust, the programming language used by the project, focused on test suites and testing patterns.

In plain words
What is it for?
Use it to write unit and integration tests, property-based tests that check many generated inputs, and tests using available tools such as cargo test, proptest, or mockall.
Why use it?
It gives Rust projects a defined approach for checking normal, edge, error, integration, and property-based cases. This helps keep tests organized and makes failures easier to diagnose.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/zircote/rlm-rs/test-engineer
Clone the repo
git clone --depth 1 https://github.com/zircote/rlm-rs

Made for: Claude Code.

Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 764 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 695266c72f31, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.claude/agents/test-engineer.md · 155 lines

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);
    }
}

Read the full file on GitHub · 155 lines

Changes

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.

  1. 2d ago First seen · 155 lines · 26 tokens per session scan A 695266c72f31

Subscribe to this mod's changes

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.

Related

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.

react/react · 33 tokens

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.

Wirasm/prp · 59 tokens

data-pipeline-engineer

Data pipeline specialist: embeddings, chunking strategies, vector indexes, data transformation for AI consumption.

yonatangross/orchestkit · 25 tokens

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.

cesarferreira/stax · 40 tokens

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…

solanabr/solana-ai-kit · 76 tokens

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.

7xuanlu/wenlan · 59 tokens