Borrowing it
Nothing to install: this file belongs to rajbos/ai-engineering-fluency. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rajbos/ai-engineering-fluency/main/.claude/agents/improve-mutation-score.mdgit clone --depth 1 https://github.com/rajbos/ai-engineering-fluencyWrote 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/rajbos/ai-engineering-fluency/improve-mutation-score)<a href="https://agentmods.dev/agents/rajbos/ai-engineering-fluency/improve-mutation-score"><img src="https://agentmods.dev/badge/agents/rajbos/ai-engineering-fluency/improve-mutation-score/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.
<a href="https://agentmods.dev/agents/rajbos/ai-engineering-fluency/improve-mutation-score"><img src="https://agentmods.dev/badge/agents/rajbos/ai-engineering-fluency/improve-mutation-score.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.01710 |
| Opus 5.5 | $0.00014 | $0.00684 |
| Sonnet 5.5 | $0.00007 | $0.00342 |
| Haiku 4.5 | $0.00003 | $0.00171 |
Grade A, and why
improve-mutation-score 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.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Improve Mutation Score Agent
Analyzes the latest Stryker mutation report and adds targeted tests to kill surviving mutants — but only where the test adds real value, not to chase a score.
Step 1 — Download the latest mutation report artifact
Use the GitHub CLI to find and download the most recent mutation-report artifact from CI:
# List recent runs that produced a mutation-report artifact
gh run list --workflow=ci.yml --limit=10 --json databaseId,displayTitle,conclusion,createdAt
# Download the artifact from the most recent successful run
gh run download <run-id> --name mutation-report --dir /tmp/mutation-report
The artifact contains:
mutation.json— full machine-readable report (this is what we analyze)report.html— human-readable HTML report
If the CI artifact is unavailable, run Stryker locally instead:
cd vscode-extension
pnpm run compile-tests
pnpm exec stryker run
# Report is written to: vscode-extension/reports/mutation/mutation.json
Step 2 — Parse the mutation report
Read /tmp/mutation-report/mutation.json (or vscode-extension/reports/mutation/mutation.json).
The structure is:
{
"mutationScore": null, // may be null — compute from counts instead
"files": {
"out/src/tokenEstimation.js": {
"mutants": [
{
"id": "1",
"mutatorName": "StringLiteral",
"replacement": "\"\"",
"location": { "start": { "line": 12, "column": 4 }, "end": { "line": 12, "column": 20 } },
"status": "Survived", // Survived | Killed | Timeout | NoCoverage
"description": "Replaced \"some string\" with \"\""
}
]
}
}
}
Extract all mutants with "status": "Survived", grouped by source file. Compute the score as:
killed / (killed + survived + timedOut) * 100
Step 3 — Map surviving mutants back to TypeScript source
The report references compiled JS files (e.g. out/src/tokenEstimation.js). Map these to their TypeScript equivalents:
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.
- yesterday First seen · 203 lines · 35 tokens per session scan A 84f8000f4d87
improve-mutation-score is an agent published in the GitHub repository rajbos/ai-engineering-fluency (119 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,710 once invoked, about $0.0001 per session on Opus 5.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-10-26.
Other agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
verify-app
Full verification - unit tests, migration check, lint, types.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.