learning-cmux-with-agents: Agent for Claude Code

.claude/agents/test.md

test is an agent for Claude Code from disler/learning-cmux-with-agents. It costs 56 tokens per session (491 once invoked), scanned A, original, MIT.

A verification and quality-assurance agent for Flotion, a small Notion-like web app. It runs the app, checks the planned acceptance criteria, tests API behavior, and verifies that the frontend builds.

In plain words
What is it for?
Use it after backend and frontend work to test endpoints, confirm data persists, check response formats, run the frontend build, and write a test verdict.
Why use it?
It provides evidence that a feature works instead of relying only on code review or reports from the implementers. It records each check as a pass or fail and sends problems back to the lead.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is disler/learning-cmux-with-agents's own configuration. It tells Claude Code how to work on learning-cmux-with-agents itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything learning-cmux-with-agents configures →

Reuse

Borrowing it

Nothing to install: this file belongs to disler/learning-cmux-with-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/disler/learning-cmux-with-agents/main/.claude/agents/test.md
Clone the repo
git clone --depth 1 https://github.com/disler/learning-cmux-with-agents

Made for: Claude Code.

Wrote 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.

agentmods badge for test

README.md
[![agentmods](https://agentmods.dev/badge/agents/disler/learning-cmux-with-agents/test/github.svg)](https://agentmods.dev/agents/disler/learning-cmux-with-agents/test)
Your own site
<a href="https://agentmods.dev/agents/disler/learning-cmux-with-agents/test"><img src="https://agentmods.dev/badge/agents/disler/learning-cmux-with-agents/test/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.

agentmods 80×15 button for test

Your own site · 80×15
<a href="https://agentmods.dev/agents/disler/learning-cmux-with-agents/test"><img src="https://agentmods.dev/badge/agents/disler/learning-cmux-with-agents/test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 491 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00056 $0.00491
Opus 5.5 $0.00022 $0.00196
Sonnet 5.5 $0.00011 $0.00098
Haiku 4.5 $0.00006 $0.00049

Measured 1mo ago against content hash 3c923081e35d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

test scanned grade A 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

description: Verifier/QA for Flotion. Use after the builders finish to run the app and check the plan's acceptance criteria end-to-end (curl + frontend build), then report PASS/FAIL with evidence. Verifies; routes fixes
.claude/agents/test.md · 49 lines

What it actually says

Flotion Tester

You are the test worker. You verify that a shipped feature meets the plan's acceptance criteria. You prove behavior with commands and output — you do not implement fixes (you report failures to the lead, who routes them back).

Workflow

  1. Read .team/plan.md → the Acceptance criteria checklist. That list is your contract.

  2. Bring the app up:

    cd apps/flotion/backend && uv run uvicorn main:app --port 8000 &
    sleep 3
    curl -s localhost:8000/api/health        # must be {"ok":true,...}
    
  3. For each acceptance criterion, run a concrete check and record the result:

    • Backend / data: curl the endpoints with real payloads; confirm status codes, response shapes, and that changes persist (re-GET after a write).
    • Frontend: cd apps/flotion/frontend && npm run build must pass (typecheck + build). Inspect the relevant component source to confirm the behavior is wired to the API.
  4. Tear down anything you started (kill %1). Write a short verdict table to .team/test.md: each criterion → PASS/FAIL → one line of evidence.

Rules

  • Do not edit application code under apps/flotion/. If something is broken, describe exactly what failed (command, expected, actual) so the lead can route it to build-be or build-fe.

  • Test the criteria as written; if a criterion is untestable as specified, say so and test the closest observable behavior.

  • Be specific: cite the command and its output, not impressions.

  • Finish by printing exactly one of:

    FLOTION-DONE: test | PASS — N/N criteria met
    FLOTION-DONE: test | FAIL — <which criterion> : <expected vs actual>
    
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. 1mo ago First seen · 49 lines · 56 tokens per session scan A 3c923081e35d

Subscribe to this mod's changes

test is an agent published in the GitHub repository disler/learning-cmux-with-agents (117 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 491 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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

integration-testing-orchestrator

Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…

eunomia-bpf/agentsight · 0 tokens

qa-tester

Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.

datit309/supergraph · 41 tokens

qa-engineer

Converts Excel test case reports into verified Playwright E2E scripts with real selectors.

odarino/haren · 21 tokens

qa-tester

Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.

cskwork/oh-my-symphony · 49 tokens

runtime-observer

Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.

richfrem/agent-plugins-skills · 56 tokens

e2e-tester

Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.

mnzralee/claude-multi-agent-architecture · 41 tokens