ryanczhang7

Audit Mutations — Security skill for Claude Code

Security community

Audit whether the tests actually verify behaviour (optional, above the bar).

How to install Audit Mutations

Installs to ~/.claude/commands/ryanczhang7-agentic-dev-harness-audit-mutations.md

Terminal

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/ryanczhang7/agentic-dev-harness/HEAD/.claude/commands/audit-mutations.md -o ~/.claude/commands/ryanczhang7-agentic-dev-harness-audit-mutations.md

Restart Claude Code, or start a new session, for it to be picked up.

What Audit Mutations does

description: Audit whether the tests actually verify behaviour (optional, above the bar) argument-hint: [path or module to audit]

Delegate to the **mutation-tester** subagent.

Scope: $ARGUMENTS (default: the code touched by the most recently completed stories)

Full coverage is already required by this harness. This asks the harder question: if the production code were subtly wrong, would any test notice?

Have the Mutation Tester run the configured `mutation` gate if there is one, and

Alternatives in Security

Maestro Odyssey — Long-running iterative cycle — one entry, seven modes (debug improve planex review security defensive ui) 530 ★
Release Audit — Use right before cutting a release — it spawns ONE fresh sibling session via CCC that audits only the JUDGMENT 130 ★
Site Metadata — Audit and refresh the docs site's SEO/social metadata (descriptions, keywords, OG cards, JSON-LD) and verify t 76 ★