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-implementgit 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-implement)<a href="https://agentmods.dev/skills/omnigent-ai/omnigent/feature-implement"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/feature-implement/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-implement"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/feature-implement.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.00017 | $0.00334 |
| Opus 5.5 | $0.00007 | $0.00134 |
| Sonnet 5.5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
feature-implement 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 6d 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.
What it actually says
Implement and test
- Implement the design. Keep the change focused on the requirements. Follow
the repository's conventions in
CLAUDE.md, including framework-owned instructions, database query names, deprecation notes, and comment style. - Test it. Read
tests/README.mdandtests/_helpers/README.md, then the nearest existing scenario. Reuse or extend existing coverage before adding setup. Put input matrices at the lowest reliable layer; add E2E only for a distinct process, transport, or browser boundary.- Map every covered CUJ to at least one test that exercises the new behavior. There is no fail-before proof for new behavior, but each test must fail if the feature were removed; a test that only passes is not coverage.
- Run the directly affected test modules and focused checks. Do not run the full repository suite locally; CI owns that.
- Check environment-derived defaults with ambient variables populated, so a test does not pass only because of the local environment.
- Assess the impact. Load
otto-impact-assessmentand apply it to the full diff. Record the results in the handoff'simpact_assessmentandtest_audit.
If a requirement turns out to be infeasible, stop building it, mark its CUJs not
covered with the reason, and continue with the rest. Then load feature-demo.
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.
- 6d ago First seen · 28 lines · 17 tokens per session scan A 3d71a8c61260
feature-implement is a skill published in the GitHub repository omnigent-ai/omnigent (10,994 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 334 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
data-scientist
!cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat .production-grade.yaml 2>/dev/null || echo "No config — using defaults".
credit-note-fixer
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
implement-universal
Harness-agnostic version of /implement. Drives a single workshop ticket through the SWE→Tester loop in ONE conversation, with the role prompts bundled as agents/software-engineer.md and agents/tester.md instead of being launched as subagents. Resolves the ticket from implementyourself/tasks/, creates an…
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
reproduce
Reproduces a paper's result, a claim, an artifact or a previous run with the target and success criterion frozen first, the canonical code path run before any substitute, exact inputs, environment, seeds and commands captured, and a verdict from a fixed set, reproduced, reproduced within tolerance, partially…
trulens-running-evaluations
Execute TruLens evaluations and view results.