property-mutation-testing-expert

property-mutation-testing-expert is a skill for Claude Code, Codex from roedyrustam/vibes-plug. It costs 103 tokens per session (2,986 once invoked), scanned A, original, MIT.

A testing guide for property-based testing and mutation testing. It helps create rules that generated inputs must satisfy and checks whether tests detect deliberately introduced bugs.

In plain words
What is it for?
Use it to find invariants, generate varied test inputs, measure mutation scores, and assess test-suite quality with tools such as fast-check, Hypothesis, Stryker, and mutmut.
Why use it?
Example tests and code-coverage percentages can miss edge cases or give false confidence. These techniques reveal gaps in what a test suite actually checks.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to find invariants, generate varied test inputs, measure mutation scores, and assess test-suite quality with tools such as fast-check, Hypothesis, Stryker, and mutmut.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/roedyrustam/vibes-plug/property-mutation-testing-expert
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.

Any agent
npx skills add roedyrustam/vibes-plug --skill property-mutation-testing-expert
Clone the repo
git clone --depth 1 https://github.com/roedyrustam/vibes-plug

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/property-mutation-testing-expert/github.svg)](https://agentmods.dev/skills/roedyrustam/vibes-plug/property-mutation-testing-expert)
Your own site
<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/property-mutation-testing-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/property-mutation-testing-expert/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 property-mutation-testing-expert

Your own site · 80×15
<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/property-mutation-testing-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/property-mutation-testing-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,986 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.00103 $0.02986
Opus 5.5 $0.00041 $0.01194
Sonnet 5.5 $0.00021 $0.00597
Haiku 4.5 $0.00010 $0.00299

Measured 7d ago against content hash b6e3e5310e57, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

skills/property-mutation-testing-expert/SKILL.md · 265 lines

How it starts

The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.

property-mutation-testing-expert — vibes-plug Skill

English | Bahasa Indonesia


English

Orchestration & Integration

Connects and orchestrates with e2e-testing-expert, autonomous-tdd-debugger, ai-code-review-autonomous, formal-spec-z3-verifier, anti-slop, typescript-expert, python-programming-expert, and production-ready-hardener to enforce mathematically rigorous test quality across the entire codebase.

Description

Production guide for two advanced testing techniques that frontier AI models unlock at unprecedented scale: (1) Property-Based Testing — generating thousands of randomized test inputs guided by algebraic properties and invariants, catching edge cases that example-based tests miss; and (2) Mutation Testing — systematically introducing bugs into the codebase and verifying that the test suite catches every one of them, measuring the actual "kill rate" of your tests. Together, these techniques expose false confidence in code coverage percentages.

Trigger Conditions

Activate this skill when:

  • Code coverage is high (>80%) but bugs still escape to production (false confidence in tests).
  • Building financial, medical, or safety-critical logic where correctness is non-negotiable.
  • The AI agent is generating test suites and needs to verify they actually catch real bugs.
  • Implementing data transformations, serialization/deserialization, or mathematical computations.
  • Auditing test quality during production-ready-hardener or zero-tech-debt-auditor phases.

Core Concepts & Patterns

1. Property-Based Testing with fast-check (TypeScript)

Instead of writing example-based tests (expect(add(2, 3)).toBe(5)), define universal properties that must hold for ALL inputs:

import fc from 'fast-check';
import { describe, it, expect } from 'vitest';

describe('Array sorting properties', () => {
  it('output has the same length as input', () => {
    fc.assert(
      fc.property(fc.array(fc.integer()), (arr) => {
        const sorted = [...arr].sort((a, b) => a - b);
        expect(sorted.length).toBe(arr.length);
      })
    );
  });

  it('output is ordered (monotonically non-decreasing)', () => {
    fc.assert(
      fc.property(fc.array(fc.integer()), (arr) => {
        const sorted = [...arr].sort((a, b) => a - b);
        for (let i = 1; i < sorted.length; i++) {
          expect(sorted[i]).toBeGreaterThanOrEqual(sorted[i - 1]);
        }
      })
    );
  });

  it('output is a permutation of input (same elements)', () => {
    fc.assert(
      fc.property(fc.array(fc.integer()), (arr) => {
        const sorted = [...arr].sort((a, b) => a - b);
        const inputCounts = countElements(arr);
        const outputCounts = countElements(sorted);
        expect(outputCounts).toEqual(inputCounts);
      })
    );
  });

  it('sorting is idempotent (sorting twice = sorting once)', () => {
    fc.assert(
      fc.property(fc.array(fc.integer()), (arr) => {
        const sortOnce = [...arr].sort((a, b) => a - b);
        const sortTwice = [...sortOnce].sort((a, b) => a - b);
        expect(sortTwice).toEqual(sortOnce);
      })
    );
  });
});

function countElements(arr: number[]): Map<number, number> {
  const counts = new Map<number, number>();
  for (const item of arr) {
    counts.set(item, (counts.get(item) ?? 0) + 1);
  }
  return counts;
}

Read the full file on GitHub · 265 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. 7d ago Changed b6e3e5310e57
  2. 12d ago First seen · 265 lines · 103 tokens per session scan A 323308aacf79

Subscribe to this mod's changes

property-mutation-testing-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (75 stars, last pushed 2d ago), licensed MIT. It adds 103 tokens to every session and 2,986 once invoked, about $0.0004 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-04.

Related

Other skills, from other repositories

test-driven-development

Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a function, fix a bug…

addyosmani/agent-skills · 92 tokens

browser-testing-with-devtools

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…

addyosmani/agent-skills · 68 tokens

spec-driven-eval

Scores how completely an implementation fulfills a PRD/spec, case by case, and produces a single comparable final grade. Invoke only when explicitly named (e.g. run spec-driven-eval); do not auto-trigger. Use when benchmarking spec-driven implementations, grading acceptance criteria, evaluating whether a feature was…

tech-leads-club/agent-skills · 123 tokens

tlc-implement

Implement a work already planned: extracts a checklist, builds it, and proves every check with an independent verifier. Use when the user says "extract a checklist", "build this ticket", "implement this spec", or "tlc-implement". Do NOT use when nobody has decided what to build, or to design the work.

tech-leads-club/agent-skills · 71 tokens

tlc-spec-lean

Spec-driven feature work that freezes obligations instead of the plan: one human-reviewed plan with EARS criteria, path, entities, interface and one-way doors, then proof-backed checks, then build, then an independent Verifier. Use when the user says "tlc-spec-lean", "plan feature", "specify feature", "write the…

tech-leads-club/agent-skills · 117 tokens

playwright-skill

Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions…

tech-leads-club/agent-skills · 95 tokens