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 agentmods add skills/omnigent-ai/omnigent/debatenpx skills add omnigent-ai/omnigent --skill debategit 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/debate)<a href="https://agentmods.dev/skills/omnigent-ai/omnigent/debate"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/debate.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.00775 |
| Opus 5 | $0.00026 | $0.00387 |
| Sonnet 5 | $0.00010 | $0.00155 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
debate 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 5d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
debate — make the two partners argue it out
Normally Debby fans a question out to both partners and shows the two answers side by side. debate goes further: it relays each partner's answer to the other partner for criticism, loops that for a configurable number of rounds, and then converges on a synthesis.
Rounds
The user picks how many rounds of back-and-forth to run. Default: 1 round. A "round" is one full cross-critique exchange (each partner sees and criticizes the other's latest answer). Honor an explicit count from the user ("debate this for 3 rounds"); otherwise run 1.
Procedure
-
Round 0 — collect the opening answers. If you do not already have a fresh answer from each partner for this question, dispatch it to both
claudeandgptin parallel viasys_session_send(ANSWER mode), give each call a stable per-partnertitle— the topic with the partner's name attached (e.g.debate-pricing-claude/debate-pricing-gpt), end your turn, and collect both withsys_read_inbox. If you already showed the user both answers this turn, reuse those as round 0. -
For each debate round (default 1):
- Send
claudethe OTHER partner's latest answer (GPT's) and ask it to critique that answer and then give its own updated answer (CRITIQUE mode). Reuse that partner's owntitleso it continues its thread. - Send
gptthe OTHER partner's latest answer (Claude's) and ask the same. Dispatch both in the same turn so they run concurrently. - End your turn; collect both updated answers with
sys_read_inbox. - Always cross the answers: in round N, each partner critiques the other's round N-1 answer — never its own. Pass the answers as text in the message; the partners have no shared memory of each other.
- Send
-
Converge. After the final round, write the synthesis yourself:
## 🟠 Claude — final <Claude's last answer, lightly trimmed> ## 🔵 GPT — final <GPT's last answer, lightly trimmed>
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.
- 5d ago First seen · 69 lines · 52 tokens per session scan A 90be81a29742
debate is a skill published in the GitHub repository omnigent-ai/omnigent (9,702 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 775 once invoked, about $0.0003 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
hugging-face-tool-builder
Use this skill when the user wants to build tool/scripts or achieve a task where using data from the Hugging Face API would help. This is especially useful when chaining or combining API calls or the task will be repeated/automated. This Skill creates a reusable script to fetch, enrich or process data.
ai-engineer
Builds production AI/ML systems — model training, fine-tuning, MLOps pipelines, model serving, evaluation frameworks, RAG optimization, and agent orchestration at scale. Use when the user asks to build, train, or deploy ML models, set up MLOps pipelines, optimize RAG systems, create inference endpoints, or design…
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".
implementation-final-review
Perform the repository's risk-tiered independent final review before implementation completion. Use only when explicitly invoked or when repository instructions require it after behavior-impacting implementation work; audit the complete task diff, supported contracts, lifecycle and security boundaries, complexity, and…
imaging-data-commons
Query and download public cancer imaging data from NCI Imaging Data Commons using idc-index. Use for accessing large-scale radiology (CT, MR, PET) and pathology datasets for AI training or research. No authentication required. Query by metadata, visualize in browser, check licenses.
datamol
Pythonic wrapper around RDKit with simplified interface and sensible defaults. Preferred for standard drug discovery including SMILES parsing, standardization, descriptors, fingerprints, clustering, 3D conformers, parallel processing. Returns native rdkit.Chem.Mol objects. For advanced control or custom parameters…