principle-sequence-verifiable-units SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
principle-sequence-verifiable-units from arjitj2/open-pstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add arjitj2/open-pstack/principle-sequence-verifiable-units@git:20260924.d4be590Pins git:20260924.d4be590 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- arjitj2/open-pstack
- Path
plugins/pstack/skills/principle-sequence-verifiable-units/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260924.d4be590, committed Sep 24, 2026
- First version recorded
- Jun 23, 2026
- Size
- 1,696 bytes
- Repository stars
- 14
- License
- MIT
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
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
# Sequence work into verifiable units Order work as a sequence of small units, each ending in a state you can check, and don't advance until the current one is green. **Why:** A break caught at the unit that caused it is cheap to localize. A break caught after a batch is buried, and you have already built further on a broken base. Sequencing those same units into a delivery a reviewer can replay turns "trust me" into "watch it go red, then green." **Execution.** In a sweep, migration, or any run of similar edits, verify each change before starting the next. Each unit is a before/after bracket: known-good state, one change, run the check, then proceed. Rebase onto clean trunk first so every check measures against the real baseline. When a lever does the edits, the per-unit check is nearly free. Run it anyway. **Delivery.** Stack commits and PRs in the order that proves the work. The canonical shape is the failing test first, then the fix on top. Other story orders are a subtraction before the reshape, a baseline capture before the treatment, the scaffold before the feature. Each commit lands on its own and the sequence reads as an argument. …
Read the whole file at its exact version.
How to install
mdr add arjitj2/open-pstack/principle-sequence-verifiable-units@sha256:5bee6caf5abdf7b0The line at the top of this page pins the label git:20260924.d4be590, 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_323b7j5n76yxvqqj)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 23, 2026 and Sep 24, 2026, about one every 31 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260924.d4be590 latest | 2026-09-24 | d4be590 | 1,696 B | A | view · diff |
| git:20260908.64f174e | 2026-09-08 | 64f174e | 2,020 B | A | view · diff |
| git:20260715.5debf23 | 2026-07-15 | 5debf23 | 2,281 B | A | view · diff |
| git:20260623.cb89fba | 2026-06-23 | cb89fba | 2,290 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 (1696 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
arjitj2/open-pstack · 14 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_323b7j5n76yxvqqj GET https://markdownregistry.com/api/v1/resolve?ref=arjitj2/open-pstack/principle-sequence-verifiable-units GET https://markdownregistry.com/api/v1/blob/5bee6caf5abdf7b05b3e7c8d3e66549d108c2f798d8155c352a1764d030816d7
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 arjitj2/open-pstack
Every file in arjitj2/open-pstack