mutation-testing

mutation-testing is a plugin for Claude Code from melodic-software/claude-code-plugins. Its token cost is not measured, scanned A, original, MIT.

A test-quality tool that changes source code in small, deliberate ways and checks whether the test suite detects each change. These altered versions are called mutants.

In plain words
What is it for?
Use it to configure and run mutation analysis, inspect surviving mutants, and find weak tests around changed code.
Why use it?
Normal test coverage shows which code ran, but not whether tests would catch common faults. Mutation testing reveals tests that execute code without checking its behavior well.

Plugin for Claude Code

Written for Claude Code: a Claude Code plugin manifest.

Good fit Use it to configure and run mutation analysis, inspect surviving mutants, and find weak tests around changed code.

Compare 6 plugins from other repositories ↓
Install in Claude Code
/plugin marketplace add melodic-software/claude-code-plugins
/plugin install mutation-testing
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.

Clone the repo
git clone --depth 1 https://github.com/melodic-software/claude-code-plugins

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 mutation-testing

README.md
[![agentmods](https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/mutation-testing/github.svg)](https://agentmods.dev/plugins/melodic-software/claude-code-plugins/mutation-testing)
Your own site
<a href="https://agentmods.dev/plugins/melodic-software/claude-code-plugins/mutation-testing"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/mutation-testing/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 mutation-testing

Your own site · 80×15
<a href="https://agentmods.dev/plugins/melodic-software/claude-code-plugins/mutation-testing"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/mutation-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
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.
Security

Grade A, and why

mutation-testing 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 18d 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.

plugins/mutation-testing/.claude-plugin/plugin.json · 22 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "mutation-testing",
  "version": "0.6.3",
  "description": "Measures whether a test suite can actually detect faults, not merely execute code: `/mutation-testing:principles` answers operator, mutant-state, and metric questions from the primary literature; `/mutation-testing:setup` verifies the ecosystem's mutation tool and writes the tracked config; `/mutation-testing:audit` runs mutation analysis on the diff, or with `--exercised` on the production code the changed tests call, and reports surviving mutants with the cause each lived, verifying that tracked source was restored and failing the run when it cannot, delegating the productive-versus-arid judgment to a fresh-context reviewer and test authoring to the test lane, and optionally persisting survivors as a findings file the review fix pass consumes.",
  "author": {
    "name": "Melodic Software",
    "email": "[email protected]"
  },
  "license": "MIT",
  "keywords": [
    "mutation-testing",
    "test-quality",
    "mutation-score",
    "test-strength",
    "coverage",
    "stryker",
    "pitest",
    "skill"
  ]
}
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. 18d ago Changed fc094d7a7d87
  2. 19d ago Changed 73cb30b4d20d
  3. 23d ago Changed 08de6cf3599e
  4. 27d ago Changed 4412484627f2
  5. 28d ago Changed 0b8d0cf89b7d
  6. 1mo ago Changed aa1a2b2c06b5
  7. 1mo ago Changed 3df6098b5dff
  8. 1mo ago Changed 5fd5f7337297
  9. 1mo ago Changed 74d42541b58e
  10. 1mo ago First seen · 22 lines scan A 0585d9e9b366

Subscribe to this mod's changes

mutation-testing is a plugin published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.