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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/omnigent-ai/omnigentnpx agentmods add skills/omnigent-ai/omnigent/resolve-publishWrote 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-publish)<a href="https://agentmods.dev/skills/omnigent-ai/omnigent/resolve-publish"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/resolve-publish/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-publish"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/resolve-publish.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.00021 | $0.03600 |
| Opus 5.5 | $0.00008 | $0.01440 |
| Sonnet 5.5 | $0.00004 | $0.00720 |
| Haiku 4.5 | $0.00002 | $0.00360 |
Grade A, and why
resolve-publish 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.
How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 3 — Commit, push, and open the pull request (author path only)
This step applies only when you authored a fix in Step 2B — it's about opening a PR. (The review path 2A adopts the existing PR instead of opening one, then goes straight to Step 4 to land it.) Once the set is genuinely green:
Check again before publishing. Once the fix and PR body are ready, repeat
Step 1's search immediately before creating a new PR, or before the final
handoff to a CI publisher. Inspect only new or changed candidates, using Step 2A
if one may cover the bug; preserve your work while evaluating it. Recheck the
state of earlier candidates too: if one merged, use the shared repro audit on
updated main before deciding whether your fix is still needed. Record the check
and decision in fix_summary. Skip this refresh for skip_push and updates to
an existing PR.
Choose the publication mode before proceeding
- Local-only (
skip_push: true) — commit the fix and stop at Step 3.2. No PR will be published automatically, so do not prepare a PR body or run Step 4. This takes precedence even when CI appended a generic publisher contract. - Workflow-owned publication (
skip_push: falseplus an explicit CI publisher contract) — do not push or make anyghwrite. Prepare and validate.omnigent/pr-body.mdusing the body-writing instructions in Step 3.4, but do not run itsgh pr createcommand. Complete the deferred live-validation preparation described in Step 4.4, then write the final handoff and stop. The publisher performs the GitHub writes; do not run the PR-facing CI/preview/review loop in the rest of Step 4. - Direct publication (no publisher contract) — perform all of Step 3, then drive the published PR through Step 4.
In workflow-owned mode, .omnigent/ is intentionally gitignored, so body
transport does not rely on the file being committed. The workflow captures
pr-body.md separately in the resolve artifact bundle alongside the committed
checkpoint, then restores it into the publication worktree before running the PR
finalizer. The finalizer validates and uses that restored file as the PR
description; without it, the publisher can only construct a less readable
fallback from machine-oriented handoff fields.
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 Changed · +29 lines e308a60b3499
- 5d ago First seen · 208 lines · 21 tokens per session scan A c090c6be1a57
resolve-publish is a skill published in the GitHub repository omnigent-ai/omnigent (10,351 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 3,600 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.
Other skills, from other repositories
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
contextual-commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
pod-init
Initialize CocoPlus project bundle in the current directory. Creates .cocoplus/ directory structure, copies all templates, initializes AGENTS.md, project.md, flow.json, and creates the initial git commit. Run this once per project before using any other CocoPlus command.
lean-review
CocoLean diff-scoped over-engineering audit — scans uncommitted git diff and applies five classification tags (delete/stdlib/native/yagni/shrink) to identify unnecessary surface area before commit.
map-diff
Analyze the impact of staged git changes against the committed Cortex function knowledge graph — shows which downstream functions are affected before you commit.
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.