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 afaraha8403/balakit --skill unmatched-workflowgit clone --depth 1 https://github.com/afaraha8403/balakitWrote 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/afaraha8403/balakit/unmatched-workflow)<a href="https://agentmods.dev/skills/afaraha8403/balakit/unmatched-workflow"><img src="https://agentmods.dev/badge/skills/afaraha8403/balakit/unmatched-workflow/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/afaraha8403/balakit/unmatched-workflow"><img src="https://agentmods.dev/badge/skills/afaraha8403/balakit/unmatched-workflow.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.00109 | $0.00585 |
| Opus 5.5 | $0.00044 | $0.00234 |
| Sonnet 5.5 | $0.00022 | $0.00117 |
| Haiku 4.5 | $0.00011 | $0.00059 |
Grade A, and why
unmatched-workflow 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 28d 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.
What it actually says
Unmatched workflow
Leading words: falsifiable done-predicate, hypothesis loop, VERIFIED NOT VERIFIED INCONCLUSIVE.
When no playbook fits, the deliverable before any code is the workflow: phases that scale rigor to the task. Inconclusive is not a pass.
Copy these steps into the todo list verbatim. Skip with skip: <reason>.
- Frame: falsifiable done-predicate, scope, rigor level (one-way doors get more). Present before a long run.
- Design the workflow: atomic units, riskiest-unknown first, verification harness before features. The first unit that writes code is the harness, not a product edit. Deleting the old API is out of scope unless the Phase 1 predicate names it. Write the phase list down.
- Run the loop: each unit is an experiment — hypothesis, smallest change, measure on the real artifact, keep or revert.
- Verify the whole against the Phase 1 predicate on the real product.
Verdicts
Each unit: VERIFIED, NOT VERIFIED, or INCONCLUSIVE. Do not hide a negative.
Pair delegated work with a parent read of the artifacts. If a worker games the gate, harden the contract. If the gate is wrong, fix the gate in its own change.
Reply contract
The playbook you designed, the rigor level and why, what is verified against the predicate, and what is still open.
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.
- 28d ago Changed · +2 lines · +10 tokens per session 7b943129f38e
- 1mo ago First seen · 50 lines · 99 tokens per session scan A df1ea6f3f926
unmatched-workflow is a skill published in the GitHub repository afaraha8403/balakit (1 stars, last pushed 29d ago), licensed MIT. It adds 109 tokens to every session and 585 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-11.
Other skills, from other repositories
designing-data-intensive-applications
Apply Martin Kleppmann-inspired data-system rules when designing reliability, scalability, consistency, replication, transactions, streams, or schema evolution.
domain-driven-design-distilled
Apply Vaughn Vernon-inspired lightweight DDD rules when using bounded contexts, subdomains, context maps, and tactical modeling without excess ceremony.
implementing-domain-driven-design
Apply Vaughn Vernon-inspired implementation DDD rules when building aggregates, domain events, repositories, application services, or context integrations.
patterns-of-enterprise-application-architecture
Apply Martin Fowler-inspired enterprise architecture rules when choosing layers, service layers, transaction scripts, domain models, repositories, mappers, or DTOs.
the-pragmatic-programmer
Apply Hunt and Thomas-inspired pragmatic programming rules when improving engineering judgment, feedback loops, DRY knowledge, orthogonality, automation, or adaptability.
working-effectively-with-legacy-code
Apply Michael Feathers-inspired legacy-code rules when changing hard-to-test code safely with characterization tests, seams, sprout methods, or wrap methods.