oh-my-agent is a harness for checking whether coding agents actually completed their work by verifying tests, required artifacts, independent reviews, and recorded decisions. It is used across multiple agent runtimes to make workflow results auditable instead of relying on an agent's own report. The catalogue add-ons provide parts of its skills, agents, hooks, MCP integrations, instructions, and plugins.
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 skills add first-fluke/oh-my-agent --skill oma-coordinationgit clone --depth 1 https://github.com/first-fluke/oh-my-agentWrote 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/first-fluke/oh-my-agent/oma-coordination)<a href="https://agentmods.dev/skills/first-fluke/oh-my-agent/oma-coordination"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-coordination/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/first-fluke/oh-my-agent/oma-coordination"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-coordination.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00024 | $0.01696 |
| Opus 5.5 | $0.00010 | $0.00678 |
| Sonnet 5.5 | $0.00005 | $0.00339 |
| Haiku 4.5 | $0.00002 | $0.00170 |
Grade A, and why
oma-coordination 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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- oma-coordination — 100% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Agent Workflow Guide
Scheduling
Goal
Guide manual multi-agent coordination for complex work that spans PM, frontend, backend, mobile, and QA responsibilities.
Intent signature
- User wants step-by-step coordination, manual agent spawning, or multi-domain work planning without full automation.
- Task spans multiple specialist agents and requires contract alignment.
When to use
- Complex feature spanning multiple domains (full-stack, mobile)
- Coordination needed between frontend, backend, mobile, and QA
- User wants step-by-step guidance for multi-agent coordination
When NOT to use
- Simple single-domain task -> use the specific agent directly
- User wants automated execution -> use orchestrator
- Quick bug fixes or minor changes
Expected inputs
- Complex feature or project goal
- Required domains and priority tiers
- Workspace/session constraints and API/data contract needs
Expected outputs
- Manual coordination sequence
- PM task decomposition, agent spawn order, monitoring guidance, and QA review step
- API/data contract alignment checkpoints
Dependencies
- PM, frontend, backend, mobile, QA, and orchestrator skills
- CLI
oma agent spawnand progress/result memory conventions
Control-flow features
- Branches by task complexity, priority tiers, dependency ordering, and whether automation is desired
- Spawns independent same-priority tasks in parallel when appropriate
- Monitors progress files and contract alignment
Structural Flow
Entry
- Confirm the task is complex enough for multi-agent coordination.
- Reuse a current plan and handoff state; use PM when task decomposition or contract changes are needed.
- Identify priority tiers and shared contracts.
- Apply the shared collaboration policy before assigning parallel work or coordinating ownership handoffs and result collection.
Scenes
- PREPARE: Define session, domains, and task decomposition needs.
- ACT: Spawn agents by priority with separate workspaces.
- VERIFY: Monitor progress and API/data contract alignment.
- FINALIZE: Run QA review and coordinate remediation.
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.
- today Changed · +1 lines f105ee45013b
- 2d ago Changed · +2 lines caf638ae4450
- 20d ago Changed · +2 lines b87e8ce67d90
- 23d ago Changed 5aa9785b08d6
- 1mo ago Changed c96493827c0a
- 1mo ago Changed · -2 lines · -12 tokens per session 5dfe35ca0aac
- 1mo ago Changed fd4982a01b0c
- 1mo ago Changed f8f2c2966171
- 1mo ago First seen · 168 lines · 36 tokens per session scan A bd5f413f067c
oma-coordination is a skill published in the GitHub repository first-fluke/oh-my-agent (1,354 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 1,696 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
ai-fleet-project-execution
AI fleet project execution (orchestrator=PM, marketing agent, backend dev agent, video agent). Fast-iteration architecture pivots and inter-agent task delegation across multi-hour sessions. Use when a user assigns a multi-agent project with "take it as a team" instruction.
fleet-helper
Shared, dependency-free Python helpers for the agent fleet - dashboard API (memory, messages, kanban), Telegram MarkdownV2 escaping, and rule-based Mail.app triage. Use to do deterministic work (fetch/filter/SQL/format/escape) in Python instead of burning model tokens doing it in the LLM turn. The dashboard token is…
kanban-audit
4 óránkénti kanban-tábla audit. Tisztítás (7+ napos done archiválás) + beakadt task-ok számon kérése (megkezdett, azóta nem mozdult -> ping az assignee-nek).
dream-engine
Éjszakai analízis-loop az aznapi memóriákról, naplóról és kanban-állapotról. Generál 4 priorizált akció-javaslatot reggelre.
folyamatos-ellenorzes
Ellenorizd: 1) Naptar - van-e meeting 1 oran belul? 2) Email - jott-e surgos level az elmult oraban? 3) Kanban - van-e mai hataridovel kartya? Ha BARMIT talalsz ami fontos, szolj a beallitott csatornan tomoren. Ha minden csendes, ne irj semmit.
change-manager
name: change-manager description: Used when the user adds a feature or incrementally changes an existing project that already has Product-Spec.md. Runs the changes/ workflow (propose, apply, verify, archive), aligned with OpenSpec-style SDD while delegating implementation to dev-planner and dev-builder. version: 1.1.0…