mutation-audit SKILL.md skillA
mutation-audit from uze-sh/uze is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add uze-sh/uze/mutation-audit@git:20261105.6f32ffePins git:20261105.6f32ffe in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- uze-sh/uze
- Path
.agents/skills/mutation-audit/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261105.6f32ffe, committed Nov 5, 2026
- First version recorded
- Nov 2, 2026
- Size
- 9,976 bytes
- Repository stars
- 4
- License
- Apache-2.0
Measuring whether UZE's tests would notice the code being wrong, with cargo-mutants - starting and monitoring `mutants.yml`, downloading the evidence, triaging each surviving mutant, writing the test a real gap needs and proving it catches the mutant. Use when someone asks about mutation testing, mutants, survivors, `missed.txt` or a "Missed mutant" annotation, whether tests really prove anything or only pass ("os testes testam mesmo?", "teste que só passa"), to audit a crate's tests, to check…
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
# Mutation audit Coverage says a line ran. A mutant asks whether a test would notice that line being wrong. The output of an audit is a triaged list and the tests it led to, never a score. ## The rules everything else serves **A test states behavior, and the mutant only points at it.** Read what the code should do from its doc comment, `docs/architecture/invariants.md`, the OpenSpec specs or the rule that owns it. A test copied from what the code does today locks in whatever bug it has. If nothing says what is right, stop and ask; that absence is a finding. **A survivor is a question.** It may be a real gap, a mutant no test could catch, or something only another crate's tests would catch. Read the code before concluding anything. **No target score.** Some mutants are equivalent, so 100% is not the goal. Compare a crate with its own earlier runs, and never write a test only to move the number. **A claim is proven by re-running the mutant.** "This test covers it" counts once that mutant reads `caught`. ## Before starting: results are public The repository is public, so a run's logs, annotations, summary and artifacts …
Read the whole file at its exact version.
How to install
mdr add uze-sh/uze/mutation-audit@sha256:522e9b7406ee329cThe line at the top of this page pins the label git:20261105.6f32ffe, 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.
[](https://markdownregistry.com/a/art_45vyfha73dcpmivw)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Nov 2, 2026 and Nov 5, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261105.6f32ffe latest | 2026-11-05 | 6f32ffe | 9,976 B | A | view · diff |
| git:20261104.617abf7 | 2026-11-04 | 617abf7 | 10,059 B | A | view · diff |
| git:20261104.b0ee375 | 2026-11-04 | b0ee375 | 9,657 B | A | view · diff |
| git:20261102.f349c45 | 2026-11-02 | f349c45 | 9,004 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9976 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 link to a raw IP address
- pass: No script tag
Source
uze-sh/uze · 4 stars · license Apache-2.0 · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_45vyfha73dcpmivw GET https://markdownregistry.com/api/v1/resolve?ref=uze-sh/uze/mutation-audit GET https://markdownregistry.com/api/v1/blob/522e9b7406ee329cebab4c3dd74fe67ea217db6c900b1819de46227f141dfa64
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.