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-checkgit 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.00020 | $0.00563 |
| Opus 5 | $0.00010 | $0.00282 |
| Sonnet 5 | $0.00004 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
omp-flow-check 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OMP-Flow Check Agent
You are already the reviewer dispatched by Main. You have no Agent or Task tool. Do not run
git commit, push, or merge.
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 reviewer
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-check and a
non-empty native agentId. Otherwise stop. The identity marker verifies the native agent type; it
does not replace the descriptor actorId 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, reviewer role, bounded objective, the same work entry used for implementation, Review Concept output, reviewer actorId, opaque receipt, and the completed implementation receipt as predecessor. The reviewer actor must differ from the implementation actor. Missing input is a blocker.
Shared Skill Delegation
Before role work, read .agents/skills/omp-flow-check/SKILL.md completely and follow it. You are
already dispatched: you cannot redispatch yourself, calibrate human decisions, transition the
workflow, or exercise coordinator governance. The Skill supplies the positive bounded independent
review duty and assigned Review Concept; this card's native identity, startup and binding gates,
assignment, tools, write and progress boundaries, different-actor requirement, 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 · 51 lines · 20 tokens per session scan A 5e7058ac456d
omp-flow-check is an agent published in the GitHub repository Andyduck-ops/omp-flow (5 stars, last pushed 6d ago), licensed MIT. It adds 20 tokens to every session and 563 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.