mutator-playwright SKILL.md skillB

mutator-playwright from mizchi/mutator is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add mizchi/mutator/mutator-playwright@git:20261118.1035b53

Pins git:20261118.1035b53 in mdr.lock. Pin the fingerprint instead.

Audit grade
B, 16 of 17 checks passed
Kind
SKILL.md skill
Repository
mizchi/mutator
Path
packages/playwright/skills/mutator-playwright/SKILL.md
Versions recorded
5
Latest version
git:20261118.1035b53, committed Nov 18, 2026
First version recorded
Oct 18, 2026
Size
9,272 bytes
Repository stars
144
License
MIT

Set up mutation testing of browser code that Playwright Test drives end to end, with mutator (@mizchi/mutator) and @mizchi/mutator-playwright, for an app served by a Vite dev server. Use when adding mutation testing to E2E tests, when `mutator --runner playwright` fails to start or finds no coverage, or when E2E mutation runs are slow.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# mutator with Playwright (E2E)

mutator compiles every mutant of the app's sources into the modules the Vite dev server serves, and the page decides which one is active. One dev server serves every mutant; each mutant run is a `playwright test` process running only the tests that reached the mutant. For mutator in general (reports, config, CI) see the `mutator` skill in `@mizchi/mutator`.

**Disabled by default.** `runner: 'auto'` selects Vitest or Jest, never Playwright. An installed `@playwright/test` or a `playwright.config.*` does not opt the project into browser mutation testing. Enable it explicitly in `mutator.config.ts`.

**Runtime warning:** Each mutant run starts a new Playwright Test process and executes browser tests. Startup and failing assertion waits make this much slower than a warm unit-test runner; large runs can take many minutes or hours. Start with a small include, sampling, a time budget and modest concurrency. Estimates appear after the baseline and type checking, and a time budget stops new runs rather than interrupting tests already in flight.

## Requirements
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_fuignmauw5zhfhsn/3e6befa5e6a2c7ecaac5ae6d4a755e294e185004d9bf362081f4b8255dd64943.json

Then /plugin install mutator-playwright@markdownregistry-fuignmauw5zhfhsn in Claude Code. It installs git:20261118.1035b53, the one graded B here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add mizchi/mutator/mutator-playwright@sha256:3e6befa5e6a2c7ec

The line at the top of this page pins the label git:20261118.1035b53, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_fuignmauw5zhfhsn.svg)](https://markdownregistry.com/a/art_fuignmauw5zhfhsn)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in mizchi/mutator/mutator-playwright since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of mutator-playwright from somewhere else? Ask it: where did my mutator-playwright come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 5 versions of this file, between Oct 18, 2026 and Nov 18, 2026, about one every 8 days. Its first recorded version is graded A and its latest B.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261118.1035b53 latest2026-11-18 1035b53 9,272 BB view · diff
git:20261018.59c8b992026-10-18 59c8b99 5,486 BA view · diff
git:20261018.3fc7d3c2026-10-18 3fc7d3c 5,378 BA view · diff
git:20261018.fa23d082026-10-18 fa23d08 4,935 BA view · diff
git:20261018.ec97e692026-10-18 ec97e69 4,676 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

B  16 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • fail: No link to a raw IP address (matched: http://127.0.0.1:4173)
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (9272 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No script tag

Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.

Source

GitHub

mizchi/mutator · 144 stars · license MIT · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_fuignmauw5zhfhsn
GET https://markdownregistry.com/api/v1/resolve?ref=mizchi/mutator/mutator-playwright
GET https://markdownregistry.com/api/v1/blob/3e6befa5e6a2c7ecaac5ae6d4a755e294e185004d9bf362081f4b8255dd64943

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from mizchi/mutator

mutation-test-loop SKILL.md skill
mizchi/mutator · .claude/skills/mutation-test-loop/SKILL.md · Close the test gaps that mutation testing finds in a change, using the mutator CLI. Use when asked to strengthen tests…
git:20261019.697b3b0 · audit A · 144 stars
mutation-test-loop SKILL.md skill
mizchi/mutator · packages/cli/skills/mutation-test-loop/SKILL.md · Close the test gaps that mutation testing finds in a change, using the mutator CLI. Use when asked to strengthen tests…
git:20261019.697b3b0 · audit A · 144 stars
mutator SKILL.md skill
mizchi/mutator · packages/cli/skills/mutator/SKILL.md · Set up and run mutator (@mizchi/mutator), diff-driven mutation testing for TypeScript/JavaScript projects tested with…
git:20261119.437efcd · audit A · 144 stars

Every file in mizchi/mutator

Browse by kind, by grade B, or by owner.