Omnigent is an open-source orchestration layer for running and coordinating different AI coding agents through one system. It is for developers who want to combine agents, apply policies and sandboxing, and continue sessions across devices. The catalogue add-ons extend its agent workflows.
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 omnigent-ai/omnigent --skill fanoutgit clone --depth 1 https://github.com/omnigent-ai/omnigentWrote 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/omnigent-ai/omnigent/fanout)<a href="https://agentmods.dev/skills/omnigent-ai/omnigent/fanout"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/fanout/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/omnigent-ai/omnigent/fanout"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/fanout.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.00043 | $0.00909 |
| Opus 5.5 | $0.00017 | $0.00364 |
| Sonnet 5.5 | $0.00009 | $0.00182 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
fanout 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 1mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fanout — safe parallel execution
Use ONLY for subtasks that are parallel-safe (no shared files, no ordering dependency).
Procedure
- Per task, create an isolated worktree:
sys_os_shell("git worktree add .worktrees/<task_id> -b polly/<task_id>"). Record the worktree path + branch in the registry (.polly/registry.json). - Dispatch one implementation sub-agent per task, scoped to its worktree:
sys_session_send(agent="claude_code"|"codex"|"opencode"|"cursor"|"hermes"|"agy", title="<task_slug>", args={purpose: "implement", input: "<task + acceptance contract + worktree path>"}). Use a short task-based title such asauth-refactororfix-sse-error, never the raw vendor name. State the scope and that it must work only inside.worktrees/<task_id>. The worker drives the task to green and opens its OWN PR for the branch. Every commit the worker authors must end with a blank line followed by the exact co-sign trailer as its final line —Co-authored-by: omnigent <[email protected]>. For a long-runningclaude_codeorcodeximplementation with an explicit completion condition, theinputmay instead be one standalone/goal <condition>command containing that same task, worktree, acceptance contract, green gates, and PR requirement. Do not use child goal mode for other workers or non-implementation purposes. Record each handle'sconversation_idin the registry. Emit the worktree +sys_session_sendtool calls in THIS turn — never end a turn having only said you will dispatch; the dispatch calls and their announcement go in the same turn. Dispatch the whole parallel-safe set, THEN (and only then) END YOUR TURN. Do not poll. - Each sub-agent runs autonomously and notifies you through the inbox when it
finishes. Collect its structured result with
sys_read_inboxand record the PR URL in the registry. If the inbox result is empty/unclear, inspect that worker conversation withsys_session_get_historybefore deciding what to do next. - Send each finished task's PR through
cross-review. - polly does NOT merge — the PR is the deliverable. When cross-review passes,
the task is done: mark it ready in the registry with its PR URL and leave it
for the human to review and merge. Never run
git merge/gh pr merge. - Remove a finished worktree (
git worktree remove) only once its PR is open and review is clean — the branch lives on the remote, so the worktree is disposable. Don't remove a worktree that still has open fix-tasks.
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.
- 1mo ago First seen · 63 lines · 43 tokens per session scan A d01d3ffd72e0
fanout is a skill published in the GitHub repository omnigent-ai/omnigent (11,046 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 909 once invoked, about $0.0002 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
configure-workspaces
Propose and generate workspace configuration files (.humanlayer/workspace.json and .humanlayer/workspace.local.json) for a repository.
implement
Drive a single workshop ticket through the inner SWE↔Tester loop. Resolves the ticket from implementyourself/tasks/, creates an implementing/from-scratch branch (a fixed default — not derived from the ticket; subsequent tickets stack on top), launches the software-engineer agent to implement it, then routes by…
describe-pr
Only use when the user explicitly invokes this skill by name.
orchestrate
Toolbox for driving HumanLayer from the CLI - log in, pick a host, launch tasks in their own worktrees, launch sessions, list tasks and their PRs, and copy, move, or upload task artifacts.
ci-commit
Only use when the user explicitly invokes this skill by name.
setup-worktree
Only use when the user explicitly invokes this skill by name.