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-implementnpx skills add Andyduck-ops/omp-flow --skill omp-flow-implementgit 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.00023 | $0.00575 |
| Opus 5 | $0.00012 | $0.00287 |
| Sonnet 5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
omp-flow-implement 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OMP-Flow Implement
Required Inputs
Fail closed unless all are available:
- task Bundle root;
- role and bounded objective;
- descriptive work entry Concept;
- allowed code scope and handoff output Concept;
- actor ID and opaque dispatch receipt;
- completed predecessor receipt when the operation requires one.
Procedure
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 Implementer: it must not dispatch or self-redispatch, govern, calibrate, transition, or selectively reinterpret coordinator clauses. The Implementer still owns the complete bounded implementation and assigned handoff: return the approved Design to practice through code, execution, and real verification, and report contradictory evidence as a Design-return signal rather than special-case reality to preserve Design authority.
- Read the work Concept first. Follow only useful links to design, decisions, sources, and relevant existing code/tests.
- Restate the bounded objective, output boundary, done conditions, and verification before editing.
- Preserve unrelated work and follow existing project patterns.
- Implement only what the work Concept requires. Report a design contradiction instead of silently redesigning the system.
- Run focused verification and broader checks required by the brief.
- Inspect the final diff for scope, generated files, debug residue, and accidental state edits.
When a Work/Handoff Concept benefits from provenance, authors may use optional OKF v0.2 prose
(sources, generated, verified, status, stale_after). Link the source Task, checkpoint or
commit, producer actor, and verification evidence where known. These fields are descriptive only;
absence does not invalidate a handoff, and they never replace the opaque operation receipt or a
different-actor Review.
Handoff
Write or update the promised handoff Concept and link it back to the work it implements. Return
DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, or BLOCKED, plus changed files, commands, test
counts, decisions, caveats, output path, actor ID, and receipt. Do not mutate runtime/session
records. The Implementer returns this assigned handoff; only Main/coordinator chooses and
dispatches the independent Review operation.
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 · 59 lines · 23 tokens per session scan A 60f422abd00e
omp-flow-implement is a skill published in the GitHub repository Andyduck-ops/omp-flow (5 stars, last pushed 6d ago), licensed MIT. It adds 23 tokens to every session and 575 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…