What is oma-coordination?

A guide for coordinating several specialist coding agents on a complex project.

It is for planning agent handoffs, ordering work, monitoring progress, and adding a final quality check.

It helps divide work between product, frontend, backend, mobile, and quality-assurance roles while keeping their contracts aligned.

oma-coordination — Skill for Claude Code and Codex by first-fluke

Install

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.

Any agent

npx skills add first-fluke/fullstack-starter --skill oma-coordination

Clone the repo

git clone --depth 1 https://github.com/first-fluke/fullstack-starter

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-coordination/github.svg)](https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-coordination)

Your own site

<a href="https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-coordination"><img src="https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-coordination"><img src="https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-coordination.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,576 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.01576
Opus 5.5	$0.00010	$0.00630
Sonnet 5.5	$0.00005	$0.00315
Haiku 4.5	$0.00002	$0.00158

Measured 14d ago against content hash b87e8ce67d90, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 14d 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.

Origin

This is a copy

100% identical to oma-coordination — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/oma-coordination/SKILL.md · 168 lines

How it starts

The opening of the file, as written. The whole thing — 168 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 spawn and 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.

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.

Read the full file on GitHub · 168 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

resources/examples.md 2.1 KB

Changes

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.

14d ago Changed · +2 lines b87e8ce67d90
25d ago Changed c96493827c0a
1mo ago Changed · -2 lines · -12 tokens per session 5dfe35ca0aac
1mo ago Changed bd5f413f067c
1mo ago First seen · 168 lines · 36 tokens per session scan A 28e249ed3983

Subscribe to this mod's changes

oma-coordination is a skill published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 1,576 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to oma-coordination, differing in 0 lines, and is treated as a copy.

Building agents Project management fastapi flutter gcp mise monorepo nextjs

oma-coordination