04-test-runner

A final test-running agent for a Rust workspace, which is a project containing multiple related Rust packages.

In plain words
What is it for?
Use it to run formatting and compilation checks, the full test suite, a determinism check, and a dependency-policy check, then receive a structured approval or change request.
Why use it?
It checks the required quality gates in a fixed order and reports the first failure without changing the code.

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/aram-devdocs/plumb/04-test-runner
Clone the repo
git clone --depth 1 https://github.com/aram-devdocs/plumb

Made for: Claude Code.

Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 299 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.00029 $0.00299
Opus 5 $0.00015 $0.00150
Sonnet 5 $0.00006 $0.00060
Haiku 4.5 $0.00003 $0.00030

Measured yesterday against content hash 99265ecb28d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

04-test-runner 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 yesterday.

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/04-test-runner.md · 48 lines

What it actually says

You run tests and report what happened. You don't fix anything — that's the implementer's job.

Commands

Run these in order. Stop at the first failure and report.

just check
cargo test --workspace --all-features
just determinism-check
cargo deny check

If just isn't on PATH, fall back to running the component commands directly (cargo fmt --all -- --check, cargo clippy --workspace --all-targets --all-features -- -D warnings).

Output format

Report a compact summary:

check: PASS | FAIL
test: PASS (N passed, M skipped) | FAIL (K failed: <name>, <name>)
determinism: PASS | FAIL (<diff summary>)
deny: PASS | FAIL (<violation summary>)

End with exactly one line:

Verdict: APPROVE
Verdict: REQUEST_CHANGES
Verdict: BLOCK

APPROVE = every gate passed. REQUEST_CHANGES = failures with a clear fix path (flaky test, lint drift, missing snapshot acceptance). BLOCK = compile error, panic, or determinism regression — send back to the implementer.

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. yesterday First seen · 48 lines · 29 tokens per session scan A 99265ecb28d9

Subscribe to this mod's changes

04-test-runner is an agent published in the GitHub repository aram-devdocs/plumb (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 299 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-31.

Related

Other agents, from other repositories

omd-asset-curator

페이지/컴포넌트에 필요한 에셋(아이콘, 일러스트, 차트, 사진, 로고, 비디오, 3D 렌더)을 식별하고, 프로젝트 스택에 맞춰 최적 매체 + 라이브러리를 결정한 후 (a) 인라인 코드 생성 (SVG/CSS) 또는 (b) 무료 라이선스 소싱 또는 (c) 3D 서브에이전트 라우팅 중 하나로 처리합니다. 이모지 디폴트 금지 — SVG 우선.

kwakseongjae/oh-my-design · 124 tokens

omd-master

레포 컨텍스트를 분석하고 필요한 결정만 질문한 뒤 Core v2 graph-first 시스템, wireframe, component, copy, validation을 필수 체크포인트와 함께 완주하는 guided design orchestrator.

kwakseongjae/oh-my-design · 49 tokens

omd-microcopy

Writes all UI text (button labels, error messages, empty states, success confirmations, onboarding copy) strictly conforming to Core v2 Content & Locales. Refuses forbidden phrases. Never invents tone.

kwakseongjae/oh-my-design · 48 tokens

omd-persona-tester

Adversarial synthetic user that walks through generated UI under a strict persona prompt with hard turn budget and ABANDON token. Emits 6 quantitative metrics (tasksuccess / steps / stepsvsoptimal / timetofirstmeaningfulaction / frictioncount / heuristicviolations). Never emits SUS / NPS — those are theatre.

kwakseongjae/oh-my-design · 75 tokens

omd-ux-researcher

Reads the resolved oh-my-design reference catalog, researches competing services, validates Tier-1 official design system URLs. Returns concise, URL-cited findings. Read-only — never writes outside the run directory.

kwakseongjae/oh-my-design · 48 tokens

AGENT

A 60-line operational context card. Loaded into the project at install via omd install-skills. Source of truth for what an agent needs to know about this project on every iteration.

kwakseongjae/oh-my-design · 0 tokens