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 agentmods add skills/diegosouzapw/omniroute/omni-context-rtknpx skills add diegosouzapw/OmniRoute --skill omni-context-rtkgit 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/omni-context-rtk)<a href="https://agentmods.dev/skills/diegosouzapw/omniroute/omni-context-rtk"><img src="https://agentmods.dev/badge/skills/diegosouzapw/omniroute/omni-context-rtk.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.00033 | $0.00653 |
| Opus 5 | $0.00016 | $0.00327 |
| Sonnet 5 | $0.00007 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
omni-context-rtk scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://localhost:20128/api/context/rtk/config \ Copies of this mod
1 near-identical copy found in the catalogue:
- omni-context-rtk — 100% identical, 24 lines differ
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Configure RTK filters, context engineering rules, and context relay settings. Test compression with real prompt samples and manage context transformation pipelines.
Authentication
All requests require a valid Bearer token or session cookie. Obtain a token via POST /api/auth/login or configure REQUIRE_API_KEY=false for local development.
Endpoints
GET /api/context/rtk/config
Get RTK compression settings
curl https://localhost:20128/api/context/rtk/config \
-H "Authorization: Bearer $OMNIROUTE_TOKEN"
PUT /api/context/rtk/config
Update RTK compression settings
curl -X PUT https://localhost:20128/api/context/rtk/config \
-H "Authorization: Bearer $OMNIROUTE_TOKEN" \
-H "Content-Type: application/json" \
-d '{}'
GET /api/context/rtk/filters
List RTK filters and load diagnostics
curl https://localhost:20128/api/context/rtk/filters \
-H "Authorization: Bearer $OMNIROUTE_TOKEN"
POST /api/context/rtk/import
Validate or install an RTK TOML schema v1 filter file
curl -X POST https://localhost:20128/api/context/rtk/import \
-H "Authorization: Bearer $OMNIROUTE_TOKEN" \
-H "Content-Type: application/json" \
-d '{}'
POST /api/context/rtk/test
Run RTK compression preview for text
curl -X POST https://localhost:20128/api/context/rtk/test \
-H "Authorization: Bearer $OMNIROUTE_TOKEN" \
-H "Content-Type: application/json" \
-d '{}'
GET /api/context/rtk/raw-output/{id}
Read retained redacted RTK raw output
curl https://localhost:20128/api/context/rtk/raw-output/{id} \
-H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/context/rtk/discover
GET context › rtk › discover
curl https://localhost:20128/api/context/rtk/discover \
-H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/context/rtk/learn
GET context › rtk › learn
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.
- 3d ago Changed · +18 lines f4f3220edb12
- 5d ago First seen · 80 lines · 33 tokens per session scan A 4dc8873993ce
omni-context-rtk is a skill published in the GitHub repository diegosouzapw/OmniRoute (61,268 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 653 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
mistake-reflection
Use when you discover you made a mistake — caught by the user, by a tool result, by your own re-reading, or by a failed check. Appends a structured entry to docs/ai/ailearnings.md and re-reads recent entries to avoid repeats.
workflow-ai-coding
Edit, validate, debug, publish, and inspect ReachAI Workflow drafts through the Workflow AI Coding REST API. Use when asked to create or modify a workflow graph, add/update/delete nodes or edges, validate GraphSpec, dry-run or debug-run a workflow, inspect trace/run output, check release readiness, publish a validated…
agentlas-auto-activation
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
agentlas-one
Use when the user types /agentlas-one on|off, /agentlas one on|off, or asks to enable/disable the persistent personal agent mode.
reachai-onboarding
Integrate Java business systems with ReachAI SDK registration, SDK instance heartbeat, gateway/embed access, and optional API Management handoff. Use when asked to connect a Spring Boot service to ReachAI, add reachai-capability-sdk or reachai-spring-boot2-starter, configure…
memory-ticketing
Use when adding Memory Events, Memory Tickets, memory-map.json, vault-references.json, PM Soul memory ownership, or Memory Curator routing to an agent repo.