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.
npx skills add OutlineDriven/odin-claude-plugin --skill mutation-campaign-configurationgit clone --depth 1 https://github.com/OutlineDriven/odin-claude-pluginWrote 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/skills/outlinedriven/odin-claude-plugin/mutation-campaign-configuration)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/mutation-campaign-configuration"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/mutation-campaign-configuration/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/skills/outlinedriven/odin-claude-plugin/mutation-campaign-configuration"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/mutation-campaign-configuration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.01608 |
| Opus 5 | $0.00034 | $0.00804 |
| Sonnet 5 | $0.00014 | $0.00322 |
| Haiku 4.5 | $0.00007 | $0.00161 |
Grade A, and why
mutation-campaign-configuration 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 6d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mutation campaign configuration
Contract
| Field | Bound contract |
|---|---|
| Trigger | The user mentions mutation testing, mewt, or muton and asks to initialize, scope, estimate, configure, validate, or optimize a campaign before execution. |
| Authority | Reversible-local. Write only mewt.toml or muton.toml. Do not create or modify the accompanying SQLite database, do not generate mutants, do not touch source files. Rollback restores the prior TOML from version control or a pre-edit snapshot. |
| Side effect | Create or update mewt.toml or muton.toml; inspect target files and estimate mutant scope read-only; measure test duration; validate readiness without interpreting completed campaign results. |
| Done | Configuration parses, intended source targets and mutant counts are estimated, test commands pass, timeout policy is justified by measurement, estimated duration is acceptable, and the project is ready for a separate campaign run. |
Inputs
- Required: Working directory containing a codebase to mutate, or an explicit
--configpath to an existingmewt.toml/muton.toml. - Required: User intent for the campaign scope (which files or components to target).
- Optional: Existing
mewt.toml/muton.tomlwith prior configuration. - Optional: Non-standard tool binary name (
mewtvsmuton).
Procedure
Phase 1: initialize and validate targets
- If no
mewt.toml/muton.tomlexists in the working directory, create one with the minimum structure:[targets]with include and ignore patterns,[test]with the test command, and[run]with mutation operators. Do not runmewt initormuton initbecause those commands create the SQLite database, which exceeds this skill's authority. Done when: the config file exists on disk. - Read the configuration:
mewt print config(ormuton print config). Done when: the configuration is parsed and its contents are recorded. - Review
[targets]include and ignore patterns. Include patterns must match only source code (e.g.,src/**/*.rs,contracts/**/*.sol). Ignore patterns must exclude tests, mocks, and generated code within included paths. Done when: include and ignore patterns are confirmed to target only intended source files. - If patterns are incorrect, edit
mewt.toml/muton.tomldirectly. Do not use CLI flags for persistent configuration. Done when: the config file reflects the corrected patterns. - Confirm:
mewt print configshows no errors andmewt print targetslists only intended files. Done when: both commands succeed and the target list is clean.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 67 lines · 68 tokens per session scan A 3f4b600261fe
mutation-campaign-configuration is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed yesterday), licensed Apache-2.0. It adds 68 tokens to every session and 1,608 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…