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 investigategit 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/investigate)<a href="https://agentmods.dev/skills/omnigent-ai/omnigent/investigate"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/investigate.svg" alt="Measured on agentmods" 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.00032 | $0.00634 |
| Opus 5 | $0.00016 | $0.00317 |
| Sonnet 5 | $0.00006 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
investigate 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 9d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
investigate — delegated read-only work
Use for any read-only task: investigation, debugging, audit, search, code understanding, architecture comparison, failure analysis, or answering a repository-specific technical question.
Procedure
- Decompose the question into one or more bounded investigation tasks. Prefer two independent lenses for ambiguous or high-stakes questions.
- Dispatch each task to
claude_code,codex,opencode,cursor,hermes,agy, orpi:sys_session_send(agent="claude_code"|"codex"|"opencode"|"cursor"|"hermes"|"agy"|"pi", title="explore-<task_slug>", args={purpose: "explore", input: "<question + exact scope + evidence requested>"}). Use a task-based title such asexplore-ci-flake, never the raw vendor name. Usepurpose: "search"only when the task is primarily external/document search. Preferpiwhen a third lens or a non-Claude/GPT model is wanted. Any worker takes an optionalargs.model(sys_list_modelsshows what each worker can run; an invalid model/worker combination fails loud at dispatch, andmodelonly applies on the dispatch that CREATES the session — a send that continues an existing title rejects it). Tell the worker to edit nothing and return file, command, URL, or line evidence. Emit thesesys_session_sendcalls in the SAME turn — do not end a turn having only said you will dispatch. - End your turn AFTER the dispatch tool calls are in flight (never before). Do not inspect files, logs, terminals, docs, or connector output yourself while the workers run.
- When workers finish, collect their completion results with
sys_read_inbox. Synthesize only from those inbox-delivered reports. Usesys_session_get_historyonly to debug an empty or unclear worker result; if reports conflict or are incomplete, dispatch a follow-upexploretask rather than resolving the conflict from your own direct inspection. - If the investigation uncovers required code changes, switch to
fanout/cross-review: dispatch animplementworker, then verify with the opposite-vendorreviewworker.
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.
- 9d ago First seen · 48 lines · 32 tokens per session scan A b6e24112de84
investigate is a skill published in the GitHub repository omnigent-ai/omnigent (9,768 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 634 once invoked, about $0.0002 per session on Opus 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
eve
Build durable backend AI agents with the eve framework. Use when creating, editing, or debugging an eve project — agent instructions, skills, tools, connections, channels, sandboxes, subagents, schedules, or evals.
typescript-testing
Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, or validating TypeScript package changes. Do not use for Python-only checks.
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.
trulens-diagnosis
Diagnose low evaluation scores and generate actionable improvement recommendations.
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.