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.
npx skills add dmae97/omk --skill principle-sequence-verifiable-unitsgit clone --depth 1 https://github.com/dmae97/omkWrote 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.
[](https://agentmods.dev/skills/dmae97/omk/principle-sequence-verifiable-units)<a href="https://agentmods.dev/skills/dmae97/omk/principle-sequence-verifiable-units"><img src="https://agentmods.dev/badge/skills/dmae97/omk/principle-sequence-verifiable-units/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.
<a href="https://agentmods.dev/skills/dmae97/omk/principle-sequence-verifiable-units"><img src="https://agentmods.dev/badge/skills/dmae97/omk/principle-sequence-verifiable-units.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00071 | $0.00377 |
| Opus 5.5 | $0.00028 | $0.00151 |
| Sonnet 5.5 | $0.00014 | $0.00075 |
| Haiku 4.5 | $0.00007 | $0.00038 |
Grade A, and why
pstack-principle-sequence-verifiable-units 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 10d 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.
This is a copy
89% identical to principle-sequence-verifiable-units — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually 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.
The sequencing complement to the prove-it-works principle skill, which keeps each check real, and the build-the-lever principle skill, which makes the per-unit check cheap.
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.
- 10d ago First seen · 18 lines · 71 tokens per session scan A 82f258b618b1
pstack-principle-sequence-verifiable-units is a skill published in the GitHub repository dmae97/omk (151 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 377 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to principle-sequence-verifiable-units, differing in 7 lines, and is treated as a copy.
pstack-principle-sequence-verifiable-units compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| pstack-principle-sequence-verifiable-unitsdmae97/omk | Skill | 151 | today | MIT | A | 71 | Claude Code |
| ci-triagecoo1white/cool-workflow | Skill | 2 | 2d ago | BSD-2-Clause | A | 66 | Claude Code, Codex |
| deploy-checkcoo1white/cool-workflow | Skill | 2 | 2d ago | BSD-2-Clause | A | 54 | Claude Code, Codex |
| design-qacoo1white/cool-workflow | Skill | 2 | 2d ago | BSD-2-Clause | A | 61 | Claude Code, Codex |
| github-copilot-upgradermicrosoft/vscode | Skill | 195k | yesterday | MIT | A | 18 | Claude Code, Codex |
| autofix-prQwenLM/qwen-code | Skill | 29k | yesterday | Apache-2.0 | A | 141 | Claude Code |
| codew-release-qa-sweepHmbown/CodeWhale | Skill | 41k | 5d ago | MIT | A | 31 | Claude Code, Codex |