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 resolve-handoffgit 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/resolve-handoff)<a href="https://agentmods.dev/skills/omnigent-ai/omnigent/resolve-handoff"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/resolve-handoff/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/resolve-handoff"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/resolve-handoff.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00023 | $0.04672 |
| Opus 5.5 | $0.00009 | $0.01869 |
| Sonnet 5.5 | $0.00005 | $0.00934 |
| Haiku 4.5 | $0.00002 | $0.00467 |
Grade A, and why
resolve-handoff 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output — the resolution handoff
The last thing in your final message must be exactly one fenced json code block — the machine-readable handoff, parsed by taking the last json fence in
the message. Same discipline as repro-agent:
- Write whatever prose summary you like above it, but the ```json block is the last chunk of the message, with nothing after its closing fence. Do not split the handoff across multiple sections or emit a second data block.
- One exception (author path): you also emit an interim handoff right after
opening the PR (Step 3.5) so the workflow can post the PR link to Linear before
Step 4 finishes. That is fine — the caller reads the last valid handoff in
the session, so this final one supersedes the interim block. The interim block
carries
pr_url+ a provisionaloutcome; this final block is authoritative. - Emit it as JSON, never YAML. Include every key below, always, even when
a value is empty (
"",[]). modemust be exactly"reviewed_existing_pr","authored_fix", or"review_remediation"— which entry path you took.outcomemust be exactly one of the string literals"fixed","partially_fixed","not_fixed","nothing_to_fix","needs_more_info"— lowercase, no other wording. This is the field the caller reads, so it must match verbatim.
{
"bug_url": "https://github.com/omnigent-ai/omnigent/issues/1234",
"mode": "authored_fix",
"outcome": "fixed",
"problem_summary": "People see internal catalog IDs in the model picker instead of readable model names.",
"solution_summary": "The model picker now shows a friendly name for every model.",
"root_cause": "picker rendered raw catalog IDs because format_label() was never called on the option list",
"fix_summary": "call format_label() when building picker options in web/src/model/picker.tsx",
"review_body": "",
"files_changed": ["web/src/model/picker.tsx"],
"facets": [
{"symptom": "picker display", "outcome": "fixed", "test_transition": "test_1234 failed: raw IDs shown → passes: friendly labels"},
{"symptom": "catalog default", "outcome": "nothing_to_fix", "test_transition": "already_fixed in #3448; skipped"}
],
"tests": {
"e2e": "",
"added": ["tests/web/model/test_picker_label.py::test_display_label"]
},
"recordings": [
{"surface": "web", "kind": "before", "path": "recordings/1234/before-picker.webm", "format": "webm",
"capture_mode": "playwright_ui",
"caption": "open the model picker → select the catalog → picker shows raw IDs"},
{"surface": "web", "kind": "after", "path": "recordings/1234/after-picker.mp4", "format": "mp4",
"capture_mode": "playwright_ui",
"caption": "open the model picker → select the catalog → picker now shows friendly names"}
],
"recording_unavailable_reason": "",
"test_audit": "Reused the display-label regression; the same assertions fail on base and pass on head. Browser reproduction evidence is staged in .omnigent/repro-evidence/; workflow upload is pending at <workflow run URL>, artifact resolve-bundle-<run-id>, path repro-evidence/. No additional browser boundary was found.",
"impact_assessment": {
"base_sha": "<full target-branch tip SHA>",
"head_sha": "<full candidate HEAD SHA>",
"worktree_state": "clean",
"risks": [
{
"files": ["web/src/model/picker.tsx"],
"behavior": "Changing labels can alter model selection or restoration",
"consumers": ["model picker", "restored sessions"],
"invariant": "Selections and restored sessions retain the same model IDs",
"check": "<exact command exercising selection and session restoration>",
"result": "passed",
"evidence": "<retained output reference, tested build and environment>"
}
],
"uncovered_boundaries": [],
"not_applicable_reason": ""
},
"remaining_work": [],
"hermetic_check": "test_picker_label re-run with ambient env vars set — still passes",
"pr_url": "https://github.com/omnigent-ai/omnigent/pull/4200",
"reviewed_pr_url": "",
"pushed_branch": "",
"ci_status": "green (all required checks pass)",
"polly_review": "clean on <full candidate HEAD SHA>: fixed null-deref; fresh review has no findings",
"ocr_review": "clean on <full candidate HEAD SHA>: no findings",
"review_cycle": {
"head_sha": "<full candidate HEAD SHA>",
"fingerprint": "<fingerprint from the final review snapshot>",
"dispositions": [
{"key": "comment:<id>", "status": "addressed", "reason": "Finding 1: null-deref fixed in <commit>; <test> passes. Finding 2: suggested fallback already exists at <path:line> and is covered by <test>, so not needed."}
]
},
"ui_preview": "labeled ui-preview on every PR; preview at https://…; posted connect instructions",
"validation_surface": "server",
"validation_prompt": "Reproduce and validate a bug fix. Steps: open the model picker in the catalog view… Before this fix, raw catalog IDs were shown. Confirm the fix by checking that friendly labels appear. Report whether each step now behaves correctly.",
"maintainer_review": "requested review from @PattaraS (issue assignee)",
"review_fingerprint": "",
"handled_review_ids": [],
"last_pushed_sha": "",
"session_id": "dc59e331-..."
}
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 Changed · +3 lines 7a44017786f5
- 1mo ago Changed · +12 lines e7ff62d9e378
- 1mo ago Changed · +3 lines ed2a01dab660
- 1mo ago Changed · +9 lines 66114b72a7af
- 1mo ago Changed · +31 lines 0791df75736c
- 1mo ago Changed · +9 lines 96a86af88762
- 1mo ago First seen · 227 lines · 23 tokens per session scan A cf955c2229fd
resolve-handoff is a skill published in the GitHub repository omnigent-ai/omnigent (11,394 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 4,672 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-09-25.
resolve-handoff compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| resolve-handoffomnigent-ai/omnigent | Skill | 11k | today | Apache-2.0 | A | 23 | Claude Code, Codex |
| fix-issueyonatangross/orchestkit | Skill | 304 | today | MIT | A | 45 | Claude Code |
| triage-issuemastra-ai/mastra | Skill | 30k | today | none | A | 14 | Claude Code, Codex |
| agent-merge-conflict-arbiterNousResearch/hermes-agent | Skill | 264k | today | MIT | A | 19 | Claude Code, Codex |
| credit-note-fixeropenai/openai-agents-python | Skill | 31k | today | MIT | A | 21 | Claude Code, Codex |
| configure-workspaceshumanlayer/humanlayer | Skill | 13k | yesterday | Apache-2.0 | A | 29 | Claude Code |
| iterate-implementationhumanlayer/humanlayer | Skill | 13k | yesterday | Apache-2.0 | A | 16 | Claude Code, Codex |