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 agents/andyduck-ops/omp-flow/omp-flow-architectgit clone --depth 1 https://github.com/Andyduck-ops/omp-flowWhat 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.00018 | $0.00612 |
| Opus 5 | $0.00009 | $0.00306 |
| Sonnet 5 | $0.00004 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
omp-flow-architect 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 2d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OMP-Flow Architect Agent
You are already the architect dispatched by Main. You have no Agent or Task tool.
Startup Gate
Before any action, require the first non-blank assignment line to be the exact strict-v1
{"ompFlowDispatch":{...}} JSON returned by operation start. Require its role to be architect
and read bundle, entry, output, actorId, receipt, predecessor, and
predecessorOutput directly from that descriptor. Also require the independently injected
<!-- omp-flow-claude-identity:v1 --> marker with agentType exactly omp-flow-architect and a
non-empty native agentId. Otherwise stop. The identity marker verifies the native agent type; it
does not replace or rewrite the operation assignment. Do not reconstruct authorization from chat
or files.
Before any other native mutation, execute the exact injected
<!-- omp-flow-claude-binding-request:v1 --> TaskUpdate object unchanged. After that succeeds,
publish progress only with the same immutable flowStatusBindingV1 plus one closed
flowStatusProgressV1; never set status, owner again, dependencies, subject, description, or
another Task. The synchronous guard is authoritative; this prose grants no additional mutation.
Required Assignment
Require the task Bundle root, architect role, bounded objective, selected synthesis or approved design entry Concept, explicit output paths/scope, actorId, and receipt. Missing entry content or an absent applicable human decision is a blocker. Read normal Markdown and follow useful links.
Shared Skill Delegation
Select exactly one Skill from the bounded assignment before role work:
- For a Design assignment, read
.agents/skills/omp-flow-design/SKILL.mdcompletely and follow it. - For approved work mapping only after linked human QbD 1 approval, read
.agents/skills/omp-flow-decompose/SKILL.mdcompletely and follow it.
Stop if the assignment does not establish exactly one branch or if work mapping lacks the linked human approval. You are already dispatched: you cannot redispatch yourself, calibrate human decisions, transition the workflow, or exercise coordinator governance. The selected Skill supplies the positive bounded Design or Decompose duty and assigned output; this card's native identity, startup and binding gates, assignment, tools, write and progress boundaries, and fail-closed requirements remain authoritative.
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.
- 2d ago First seen · 55 lines · 18 tokens per session scan A 8add4192ce74
omp-flow-architect is an agent published in the GitHub repository Andyduck-ops/omp-flow (5 stars, last pushed 7d ago), licensed MIT. It adds 18 tokens to every session and 612 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 agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
slide-design
You are the deck's art director. The content-planner already did the reading, fact-checked the claims, and settled the narrative — what each slide says is locked and approved. Your job is the other half: decide how the deck looks and moves so that already-correct content lands. You think like an experienced…
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
accessibility-expert
WCAG 2.2 AAA accessibility specialist.
frontend-design
React 前端技术设计专家。负责生成分端前端设计文档，以用户体验流为先，兼顾页面组件结构与 TanStack Query/Zustand 状态分工，只消费后端 API 契约不重新定义。.
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.