ai-engineering-fluency: Agent for Claude Code

.claude/agents/improve-mutation-score.md

improve-mutation-score is an agent for Claude Code from rajbos/ai-engineering-fluency. It costs 35 tokens per session (1,710 once invoked), scanned A, original, MIT.

A mutation-testing helper that reads a Stryker report and adds tests for surviving mutants. Mutation testing changes code in small ways to check whether tests would catch those changes.

In plain words
What is it for?
Use it to download or generate the latest mutation report, inspect surviving mutants, and add targeted tests where they improve protection.
Why use it?
A passing test suite can still miss important behaviour. This focuses new tests on meaningful gaps instead of adding tests only to raise a score.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is rajbos/ai-engineering-fluency's own configuration. It tells Claude Code how to work on ai-engineering-fluency 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 ai-engineering-fluency configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/rajbos/ai-engineering-fluency/main/.claude/agents/improve-mutation-score.md
Clone the repo
git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency

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 improve-mutation-score

README.md
[![agentmods](https://agentmods.dev/badge/agents/rajbos/ai-engineering-fluency/improve-mutation-score/github.svg)](https://agentmods.dev/agents/rajbos/ai-engineering-fluency/improve-mutation-score)
Your own site
<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.

agentmods 80×15 button for improve-mutation-score

Your own site · 80×15
<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>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,710 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00035 $0.01710
Opus 5.5 $0.00014 $0.00684
Sonnet 5.5 $0.00007 $0.00342
Haiku 4.5 $0.00003 $0.00171

Measured yesterday against content hash 84f8000f4d87, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/agents/improve-mutation-score.md · 203 lines

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:

Read the full file on GitHub · 203 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. yesterday First seen · 203 lines · 35 tokens per session scan A 84f8000f4d87

Subscribe to this mod's changes

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.

Related

Other agents, from other repositories