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 feature-publishgit 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/feature-publish)<a href="https://agentmods.dev/skills/omnigent-ai/omnigent/feature-publish"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/feature-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/feature-publish"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/feature-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.00024 | $0.00936 |
| Opus 5.5 | $0.00010 | $0.00374 |
| Sonnet 5.5 | $0.00005 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
feature-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 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish and drive the PR
Commit
Commit the implementation and its tests on the working branch with the
repository's conventions, signed off (git commit -s). Stage paths explicitly
and check git diff --cached --stat: never commit recordings/ or
.omnigent/ files. Read the staged diff for redundant comments. If a commit
hook changed tested files, rerun their checks. If the checkout has
.github/scripts/pr-template/hygiene.py, run it with --base origin/main.
Choose the publication mode
- Local-only (
skip_push: true): stop after committing. Report the branch inpushed_branchand leavepr_urlempty; do not prepare a PR or drive one. The outcome ispartially_implemented, with publishing and the PR loop inremaining_work. - Workflow-owned (a CI publisher contract is appended to your instructions):
do not push or make any
ghwrite. Write and validate.omnigent/pr-body.md(below), write the final handoff, and stop. The workflow publishes the PR and runs the PR loop. - Direct (no publisher contract): push the branch, open the PR, then drive it (below).
When .omnigent/pr-gate.json exists, make every PR write (create, edit, comment,
review, ready) with the pr.py helper CI supplies, at the path given in the
publisher contract. Keep Git pushes on the supplied credential. Never decode,
search for, or export another token, and never change credential configuration.
The PR is always ready for review, never a draft, including when a recording is blocked.
PR body
Copy .github/pull_request_template.md to .omnigent/pr-body.md and fill it
in, keeping every heading and checkbox row:
- First lines:
Implements <feature_url>and<!-- omnigent-feature-managed -->. Do not use a closing keyword against a Linear URL. - Summary: a 1–2 sentence plain-language description of what users can now do, then subsections Design, Alternatives considered, CUJs covered, and CUJs not covered (and why).
- Test Plan: each covered CUJ with the tests that exercise it, plus the impact-assessment checks, as short bullets.
- Demo: the recordings for each covered CUJ, labelled by CUJ ID. Upload them
as GitHub attachments when your environment can, otherwise link where they
live (the CI artifact bundle). For a CUJ with a blocked recording, give the
blocker and the manual test steps instead. When a Linear key is available,
also attach the recordings to the ticket (GraphQL
fileUpload+attachmentCreate). - Check Feature, plus UI / frontend change when the UI 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.
- today First seen · 80 lines · 24 tokens per session scan A 9d7797801dcb
feature-publish is a skill published in the GitHub repository omnigent-ai/omnigent (10,855 stars, last pushed today), licensed Apache-2.0. It adds 24 tokens to every session and 936 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-10-17.
Other skills, from other repositories
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.
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.
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.
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.
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…
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.