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-workflow-maintainernpx skills add Andyduck-ops/omp-flow --skill omp-flow-workflow-maintainergit 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-workflow-maintainer)<a href="https://agentmods.dev/skills/andyduck-ops/omp-flow/omp-flow-workflow-maintainer"><img src="https://agentmods.dev/badge/skills/andyduck-ops/omp-flow/omp-flow-workflow-maintainer.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.00391 |
| Opus 5 | $0.00014 | $0.00196 |
| Sonnet 5 | $0.00006 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
omp-flow-workflow-maintainer 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.
What it actually says
OMP-Flow Workflow Maintainer
Use this Skill only for a bounded Workflow Library maintenance Task. The Task Bundle is the source of purpose, boundaries, evidence, output, and human decisions.
Method
- Read the Task entry and
.omp-flow/workflow/index.mdwhen it exists. Follow only useful ordinary links to the affected Workflow Markdown, authored fragments, archived Task evidence, Reviews, handoffs, and Sleep Candidates. - Separate repository facts, repeated practice findings, contrary evidence, local exceptions, applicability boundaries, and unresolved questions.
- Write the smallest candidate revision in the assigned Task output. State the affected Workflow or fragment, proposed prose change, expected benefit, counterexample, regression risk, and replay or verification plan.
- Do not edit canonical production Workflow policy, Skills, Hooks, or Runtime as an automatic result of this maintenance analysis. Promotion is a separate bounded Work after independent review and human decision.
- If a production change is authorized, the Main session creates the bounded Work and uses
operation start; forward its complete returned assignment unchanged. Never manufacture an assignment, actor ID, receipt, dependency, or runtime phase.
Boundaries
- Do not parse Workflow Markdown, folder names, headings, links, or frontmatter into machine state.
- Do not create a graph runtime, route schema, exact-topology identity, second dispatcher, or automatic Workflow selector.
- Do not let model name alone select Lite or bypass a required boundary.
- Do not turn one Task-specific observation into a global Workflow rule without replay, contrary evidence, applicability limits, independent review, and human calibration.
- Do not spawn another workflow sub-agent.
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 · 37 lines · 28 tokens per session scan A 0f7fb3bada68
omp-flow-workflow-maintainer is a skill published in the GitHub repository Andyduck-ops/omp-flow (6 stars, last pushed 8d ago), licensed MIT. It adds 28 tokens to every session and 391 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…