OmniRoute is an AI gateway that gives coding agents one endpoint for accessing models from many providers, with quota-aware fallback between them. It is for people using Claude Code, Codex, Cursor, OpenCode, Cline, Copilot, and similar tools who want a single route to their available AI models.
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 diegosouzapw/OmniRoute --skill validate-release-greengit clone --depth 1 https://github.com/diegosouzapw/OmniRouteWrote 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/diegosouzapw/omniroute/validate-release-green)<a href="https://agentmods.dev/skills/diegosouzapw/omniroute/validate-release-green"><img src="https://agentmods.dev/badge/skills/diegosouzapw/omniroute/validate-release-green/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/diegosouzapw/omniroute/validate-release-green"><img src="https://agentmods.dev/badge/skills/diegosouzapw/omniroute/validate-release-green.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.00047 | $0.00595 |
| Opus 5.5 | $0.00019 | $0.00238 |
| Sonnet 5.5 | $0.00009 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
validate-release-green 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 yesterday.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Release-Green
Read ../_shared/base-green.md before interpreting remote status or attributing
a failure. Resolve the current base and candidate SHA; use an isolated worktree.
The observer validates that working tree, not an abstract branch name.
Select and execute the actual profile
Inspect scripts/quality/validate-release-green.mjs, its npm entrypoint and the
candidate's workflows before choosing flags. On candidates that provide them:
npm run check:release-green -- --quick: partial fast diagnosis.npm run check:release-green -- --full-ci --with-build --hermetic --json: the observer's broader static/test/package profile; this is still not a promise of parity with every workflow lane.
The versioned static gate manifest, if present, describes static scan membership, not all observer or admission jobs. Report unmodeled coverage explicitly.
Build in a worktree with physical dependencies, never an external node_modules symlink. Preserve stdout/stderr, process receipts and the validator's own exit. Read the report even when the outer job is green. Missing, contradictory, stale, cancelled or timed-out evidence cannot establish PASS.
Interpret and compare
HARD is the observer's blocking classification; DRIFT is its diagnostic bucket. Neither class alone proves causality. Compare the same requirement on the exact base before calling a defect contributor-introduced. A ratchet classified as advisory locally can still block in the applicable CI workflow.
A green local profile means only that profile passed. Record remaining lanes, including relevant Node/Vitest suites, coverage, security, build, package/boot and external checks. Do not stamp merge-ready or pre-greened based on a focused run, a draft skip, a closed incident or an old head SHA.
For machine reports, use scripts/ci/release-green-result.mjs when available on
the candidate. It checks the observed exit, exact SHA and event/profile; supply
the values from the run rather than inventing an exit code. The report verifier
does not establish that omitted workflow requirements ran.
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.
- yesterday First seen · 57 lines · 47 tokens per session scan A 5b2b4785b0be
validate-release-green is a skill published in the GitHub repository diegosouzapw/OmniRoute (72,710 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 595 once invoked, about $0.0002 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-03.
Other skills, from other repositories
transport-release-gate
Run a quality gate over an SAP transport request before it is released — collect the TR's objects, check for inactive objects and foreign locks, run syntax checks, ATC, and unit tests, then produce a structured go/no-go report. Use whenever the user wants to release a transport, asks "is this TR safe to release?"…
dev-ship
Fechamento de feature — verificação goal-backward antes de declarar pronto. Roda Must-Haves do PLAN.md, executa o demo script, revisa o diff completo procurando bugs e restos (debug logs, TODOs, código morto), passa lente de segurança nos arquivos tocados, escreve SUMMARY.md e arquiva o plano. Use quando o usuário…
matilha-gather
Use when completed subprojects are ready to merge — validates SP-DONE.md strict gates, merges --no-ff in mergeorder, runs per-SP regression, updates wave-NN-status.md.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer…
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.