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 agentmods add skills/andyduck-ops/omp-flow/omp-flow-designnpx skills add Andyduck-ops/omp-flow --skill omp-flow-designgit clone --depth 1 https://github.com/Andyduck-ops/omp-flowWrote 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/andyduck-ops/omp-flow/omp-flow-design)<a href="https://agentmods.dev/skills/andyduck-ops/omp-flow/omp-flow-design"><img src="https://agentmods.dev/badge/skills/andyduck-ops/omp-flow/omp-flow-design.svg" alt="Measured on agentmods" 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 | $0.00028 | $0.00634 |
| Opus 5 | $0.00014 | $0.00317 |
| Sonnet 5 | $0.00006 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
omp-flow-design 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OMP-Flow Design
Preconditions
- The assignment identifies the Bundle root, role, objective, selected synthesis entry Concept, allowed output paths, actor ID, and receipt.
- Source provenance needed for the design is readable through ordinary links.
Procedure
Before native dispatch, only Main/coordinator may dispatch, correlate operations/receipts, obtain or record human calibration, and choose a workflow transition. Those coordinator actions are inapplicable to an already-dispatched Architect: it must not dispatch or self-redispatch, govern, calibrate, transition, or selectively reinterpret coordinator clauses. The Architect still owns the complete bounded Design responsibility and assigned PRD/Design/decision/interface outputs: explain each proposed component's concrete causal purpose in plain language, without relying on its own terminology, and solve the evidenced principal contradiction rather than a secondary or invented mechanism.
- In Main/coordinator context only, dispatch the native Architect with Bundle root, selected
synthesis entry, bounded objective, relevant linked Concepts, explicit output ownership, actor
ID, and receipt. Create the operation first and forward its complete returned assignment
unchanged with native item
id = actor_id = actorIdand matching descriptor role. Preserve the strict v1ompFlowDispatchdescriptor as the first non-blank line. - Rewrite
prd.mdinto observable requirements, non-goals, constraints, acceptance criteria, and unresolved product decisions. Remove temporary brainstorm duplication. - Write
design.mdwith components, interfaces, data flow, state ownership, error behavior, migration/compatibility, verification strategy, and rejected alternatives. - Add linked decision, interface, brief, or finding Concepts only when they improve navigation or reuse. Their directories and filenames are descriptive, not tiers or identifiers.
- Express binding constraints precisely and retain links to the synthesis or source Concepts.
- Review PRD, Design, and linked Concepts for contradictions, placeholders, unowned decisions, and requirements with no verification path.
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.
- 4d ago First seen · 58 lines · 28 tokens per session scan A 4e5aaf2b2484
omp-flow-design is a skill published in the GitHub repository Andyduck-ops/omp-flow (5 stars, last pushed 8d ago), licensed MIT. It adds 28 tokens to every session and 634 once invoked, about $0.0001 per session on Opus 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-08-31.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
okx-task-watch
监听任务进展 / 帮我盯着任务 / 任务有动静告诉我 / 历史消息 / 未读消息 / 未决策 / 待决策 / 继续监听 / task watch / user watch / monitor task progress / catch me up on tasks / outstanding decisions — OKX A2A user-session task-notification monitor: live long-poll via okx-a2a user watch (also drains backlog of past/missed/unread events on entry) plus…
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.