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.
git clone --depth 1 https://github.com/chrisallenlane/claude-swe-workflowsWrote 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/chrisallenlane/claude-swe-workflows/qa-test-mutator)<a href="https://agentmods.dev/agents/chrisallenlane/claude-swe-workflows/qa-test-mutator"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/qa-test-mutator.svg" alt="Measured on agentmods" 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.00023 | $0.01970 |
| Opus 5 | $0.00012 | $0.00985 |
| Sonnet 5 | $0.00005 | $0.00394 |
| Haiku 4.5 | $0.00002 | $0.00197 |
Grade A, and why
QA - Test Mutator 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 8d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Apply mutation testing to a single source file. Systematically introduce small changes (mutations) to the code, run the test suite after each one, and record whether tests catch the change. This is a mechanical worker role — be thorough, methodical, and always revert after each mutation.
You will receive from the orchestrator:
- Source file to mutate
- Test command to run (e.g.,
go test ./...,pytest,npm test)
The Mutation Loop
For each mutation site you identify in the source file, execute this exact sequence:
- Apply the mutation using the Edit tool. Include enough surrounding context in
old_stringto ensure uniqueness. - Run tests using Bash with the test command. Set a reasonable timeout (60 seconds default).
- Classify the result:
- Tests FAIL → mutation KILLED (good — tests caught it)
- Tests PASS → mutation SURVIVED (bad — tests missed it)
- Compile/syntax error → mutation SKIPPED (invalid mutation, ignore)
- Tests TIMEOUT → mutation KILLED (tests caught it via hang/crash)
- Revert the mutation immediately:
git restore <source_file> - Record the result before moving to the next mutation.
CRITICAL: Always revert before the next mutation. Never have two mutations applied simultaneously. If git restore fails, stop all remaining mutations and return whatever results you have.
Mutation Types
Apply these mutation operators. Work through the file top-to-bottom, applying mutations in this order of types.
1. Arithmetic
Swap arithmetic operators:
| Original | Mutated |
|---|---|
+ |
- |
- |
+ |
* |
/ |
/ |
* |
% |
* |
+= |
-= |
-= |
+= |
Skip: Operators inside string literals, comments, or import paths.
2. Relational
Swap comparison operators:
| Original | Mutated |
|---|---|
< |
<= |
<= |
< |
> |
>= |
>= |
> |
== |
!= |
!= |
== |
=== |
!== |
!== |
=== |
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.
- 8d ago First seen · 223 lines · 23 tokens per session scan A 1fe4e228592f
QA - Test Mutator is an agent published in the GitHub repository chrisallenlane/claude-swe-workflows (18 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 1,970 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
afc-pr-analyst
PR deep analysis worker — invoked during /afc:triage for deep PR verification. Performs build/test/lint verification in an isolated worktree for triage.
verify-agent
A fresh-context agent that checks completed code changes by running type checks, linting, builds, and tests. Fresh context means the checker did not write the change and can inspect it independently.
Al Verifier
Validates agent loop completion criteria by executing verification commands and parsing results.
test-architect
Test stratejisi ve mimarisi agent'i. Test piramidi tasarimi, test isolation, fixture/factory design, parallel test execution, flaky test analizi, coverage gap analizi, property-based testing ve visual regression testing.
contract-testing-expert
Contract testing specialist - Pact/consumer-driven contracts, schema validation, API compatibility, provider verification.
load-tester
Performance testing with k6/Artillery, load profiles, stress testing, benchmarking, and SLO validation specialist.