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-inputsgit 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-inputs)<a href="https://agentmods.dev/skills/omnigent-ai/omnigent/resolve-inputs"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/resolve-inputs/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-inputs"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/resolve-inputs.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.00022 | $0.01957 |
| Opus 5.5 | $0.00009 | $0.00783 |
| Sonnet 5.5 | $0.00004 | $0.00391 |
| Haiku 4.5 | $0.00002 | $0.00196 |
Grade A, and why
resolve-inputs 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start a Resolve run
Read only the resource matching the work source before preflight:
sessionorci_link: read reproduction.md.review_pr: load the sharedotto-review-remediationskill. It takes precedence over repro recovery and candidate discovery.bug_urlalone: read ticket-only.md.
Use read_skill_file with this skill name and the relative filename, or read
relative to the directory supplied by the native Skill tool. The agent bundle
may live outside the target checkout; do not resolve these files against cwd.
After preflight, load resolve-investigate in every mode. Apply it before the
repro audit or choosing a fix. After resolve-repro-audit for reproduction-driven
work, read
existing-fix.md before choosing author or review. Skip discovery
in review-remediation mode. Load resolve-impact-assessment for every mode.
Input contract
You are invoked with exactly one work source:
session(a link or bare id) — the repro-agent session, e.g.http://localhost:6767/c/dc59e331-...or justdc59e331-.... This is the local path: you were launched right afterdev/repro.py. Read the session to recover the handoff (see below).ci_link(a CI run URL) — e.g.https://github.com/omnigent-ai/omnigent-internal/actions/runs/30974269184. This is the CI path: repro-agent ran in a throwaway CI worktree that no longer exists, so you recover everything from the run itself (see below).review_pr(a canonical GitHub PR URL) — a trusted human requested changes on a PR already filed or modified by resolve-agent. This is review-remediation mode: skip reproduction recovery and follow the dedicated procedure below.bug_urlalone (nosession,ci_linkorreview_pr) — ticket-only mode: nobody reproduced this bug in the app, and there is no handoff to recover. The ticket itself is the brief. Otto Health files these about the Otto CI wrappers (labelsource:otto-health); see "Ticket-only mode" below.
What ships with it
3 files 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.
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 Changed 6deba47fc6f7
- 12d ago Changed · +2 lines ba9904f3e141
- 15d ago Changed a9bcc4d55205
- 21d ago First seen · 131 lines · 22 tokens per session scan A ca397cfb70e7
resolve-inputs is a skill published in the GitHub repository omnigent-ai/omnigent (10,832 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 1,957 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
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…
triage-issue
First-contact triage for a GitHub issue.
calldiff
Call-graph evidence from git via the calldiff CLI: which functions reach a symbol, and how a change moved the call structure. Use when you need blast radius before editing (does anything reach this function, and by what path), when scoping which files a change really touches, or when reviewing a diff whose risk is…
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
credit-note-fixer
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
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…