audit-state-machines SKILL.md skillA
audit-state-machines from doodledood/manifest-dev is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add doodledood/manifest-dev/audit-state-machines@git:20261107.a10d070Pins git:20261107.a10d070 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- doodledood/manifest-dev
- Path
claude-plugins/manifest-dev/skills/audit-state-machines/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261107.a10d070, committed Nov 7, 2026
- First version recorded
- Nov 7, 2026
- Size
- 3,289 bytes
- Repository stars
- 78
- License
- MIT
Find every implicit and explicit state machine in a codebase, model each one formally, and report every bug the model shows and the code confirms — a bad state that can be reached, a forbidden transition, a state with no way out — with its fix and an offer to turn the findings into Tickets. Changes no code. Use when the user asks to audit state machines, find implicit state machines, check status or lifecycle logic across an app, or find status or lifecycle bugs that span several files.
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
Audit a codebase for state-machine bugs. A state machine is a value whose changes follow a lifecycle — a status, or flags whose combinations act as states — and `../review-code/references/code-bugs.md` → *State machines* says how to find one, rebuild it, check it and confirm what the check finds. figure-out runs the audit with its whole investigation discipline; this skill adds the brief below and the offer at the end. Invoke the figure-out skill with the brief below, the arguments given, `--autonomous` and `--no-docs`. `--no-docs` keeps figure-out's project-document writes out of the audited project; forward `--no-log` when given. With no path or area, the scope is the whole repository. With no codebase in reach, say so and stop. Brief: > Audit [the scope] for state machines, implicit and explicit, following `../review-code/references/code-bugs.md` → *State machines*. Every bug you find counts, whether or not anything changed recently: this is an audit, not a review of a change. Machines written as instructions count too, checked as that section says. > …
Read the whole file at its exact version.
How to install
mdr add doodledood/manifest-dev/audit-state-machines@sha256:d513513454b32e77The line at the top of this page pins the label git:20261107.a10d070, 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_keonq22fnv6jn566)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, all committed on Nov 7, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261107.a10d070 latest | 2026-11-07 | a10d070 | 3,289 B | A | view · diff |
| git:20261107.98bb4b6 | 2026-11-07 | 98bb4b6 | 3,250 B | A | view · diff |
| git:20261107.5a0076f | 2026-11-07 | 5a0076f | 3,540 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 (3289 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
doodledood/manifest-dev · 78 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_keonq22fnv6jn566 GET https://markdownregistry.com/api/v1/resolve?ref=doodledood/manifest-dev/audit-state-machines GET https://markdownregistry.com/api/v1/blob/d513513454b32e77e74008678b0cde99a5ecee03604d0be68311c916d5193345
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.