mutation-testing
Mutation-testing configures mewt or muton campaigns for testing code robustness through mutation injection. Use this skill when a user mentions mewt, muton, or mutation testing, or needs help configuring, optimizing, or scoping a mutation testing campaign. The skill guides users through initialization, mutant generation, timeout tuning, and campaign optimization across languages like Rust, Solidity, Go, TypeScript, JavaScript, and TON smart contracts.
git clone --depth 1 https://github.com/trailofbits/skills /tmp/mutation-testing && cp -r /tmp/mutation-testing/plugins/mutation-testing/skills/mutation-testing ~/.claude/skills/mutation-testingSKILL.md
# Mutation Testing — Campaign Configuration (mewt/muton) > **Note**: muton and mewt share identical interfaces but target different languages — mewt for general-purpose languages (Rust, Solidity, Go, TypeScript, JavaScript), muton for TON smart contracts (Tact, Tolk, FunC). All examples use `mewt` commands, but they work exactly the same with `muton`. File names change accordingly: `mewt.toml` → `muton.toml`, `mewt.sqlite` → `muton.sqlite`. ## When to Use Use this skill when the user: - Mentions "mewt", "muton", or "mutation testing" - Needs to configure or optimize a mutation testing campaign - Wants to run `mewt run` and needs help getting set up first ## When NOT to Use Do not use this skill when the user: - Wants to analyze or report on completed campaign results - Asks about tests or coverage without mentioning mutation testing --- ## Quick Start Load [workflows/configuration.md](workflows/configuration.md) — a 5-phase guide from `mewt init` to a validated, ready-to-run campaign. **General question or unfamiliar command?** Run `mewt --help` or `mewt <subcommand> --help`, then assist. --- ## Reference Index | File | Content | |------|---------| | [workflows/configuration.md](workflows/configuration.md) | 5-phase guide: init, scope, optimize, validate, run | | [references/optimization-strategies.md](references/optimization-strategies.md) | Per-file targeting, two-phase campaigns, mutation type filtering | --- ## Essential Commands ```bash # Initialize and mutate mewt init # Create mewt.toml and mewt.sqlite mewt mutate [paths] # Generate mutants without running tests mewt run [paths] # Run the full campaign # Inspect configuration and scope mewt print config # View effective configuration mewt print targets # Table of all targeted files mewt print mutations --language [lang] # Available mutation types mewt status # Mutant count and per-file breakdown # Investigate specific mutants mewt print mutants --target [path] # All mutants for a file mewt print mutants --severity high # Filter by severity mewt print mutant --id [id] # View mutated code diff mewt test --ids [ids] # Re-test specific mutants ``` --- ## What Results Mean - **Caught/TestFail**: Tests detected the mutation (good) - **Uncaught**: Mutation survived — indicates untested logic - **Timeout**: Tests took too long, inconclusive - **Skipped**: A more severe mutant already failed on the same line
Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches AI agents running in CI/CD pipelines, including env var intermediary patterns, direct expression injection, dangerous sandbox configurations, and wildcard user allowlists. Use when reviewing workflow files that invoke AI coding agents, auditing CI/CD pipeline security for prompt injection risks, or evaluating agentic action configurations.
Clarify requirements before implementing. Use when serious doubts arise.
Understand a codebase before looking for bugs in it - what each function assumes, what it guarantees, and what it depends on elsewhere. Use when starting an audit, threat model, or architecture review on unfamiliar code, and before any vulnerability-hunting pass.
Scans Algorand smart contracts for 11 common vulnerabilities including rekeying attacks, unchecked transaction fees, missing field validations, and access control issues. Use when auditing Algorand projects (TEAL/PyTeal).
Prepares codebases for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments). Use when preparing your own codebase to be audited by someone else, getting a repository review-ready before an external security review, deciding what to fix before auditors start, or asking what assessors need from a project. For understanding unfamiliar code you are about to audit, use audit-context-building instead.
Scans Cairo/StarkNet smart contracts for 6 critical vulnerabilities including felt252 arithmetic overflow, L1-L2 messaging issues, address conversion problems, and signature replay. Use when auditing StarkNet projects.
Systematic code maturity assessment using Trail of Bits' 9-category framework. Analyzes codebase for arithmetic safety, auditing practices, access controls, complexity, decentralization, documentation, MEV risks, low-level code, and testing, then produces a scorecard with evidence-based ratings and a priority-ordered roadmap. Use when assessing or scoring the maturity of a smart contract or blockchain codebase, producing a maturity scorecard or evaluation, or judging how mature, well-tested, or well-documented such a project is against a rubric.
Scans Cosmos SDK blockchain modules and CosmWasm contracts for consensus-critical vulnerabilities — chain halts, fund loss, state divergence. 25 core + 16 IBC + 10 EVM + 3 CosmWasm patterns. Use when auditing custom x/ modules, reviewing IBC integrations, or assessing pre-launch chain security. Updated for SDK v0.53.x.