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/cli-providersnpx skills add diegosouzapw/OmniRoute --skill cli-providersgit clone --depth 1 https://github.com/diegosouzapw/OmniRouteWhat 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.00036 | $0.02029 |
| Opus 5 | $0.00018 | $0.01014 |
| Sonnet 5 | $0.00007 | $0.00406 |
| Haiku 4.5 | $0.00004 | $0.00203 |
Grade A, and why
cli-providers 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cli-providers — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Manage provider connections from the CLI: list available/configured providers, add, test, test-all, validate, rotate API keys, and view per-provider metrics.
Quick install
npm install -g omniroute # or: npx omniroute
omniroute --version
Subcommands
provider-cmd provider [subcommand]
Manage provider connections (use
Example:
omniroute provider-cmd provider [subcommand]
providers
Example:
omniroute providers
providers available
Show available providers in the OmniRoute catalog
Flags:
--json--search <query>-q, --q <query>--category <category>
Example:
omniroute providers available
providers list
List configured provider connections
Flags:
--json
Example:
omniroute providers list
providers test <idOrName>
Test a configured provider connection
Flags:
--json
Example:
omniroute providers test <idOrName>
providers test-all
Test all active provider connections
Flags:
--json
Example:
omniroute providers test-all
providers validate
Validate local provider configuration without calling upstream
Flags:
--json
Example:
omniroute providers validate
providers rotate <idOrName>
Flags:
--new-key <key>--from-env <VAR>--oauth--yes--skip-test--dry-run
Example:
omniroute providers rotate <idOrName>
providers status
Flags:
--provider <name>--json
Example:
omniroute providers status
providers metrics
Flags:
--provider <id>--connection-id <id>--period <p>--metric <m>--sort-by <field>--limit <n>--watch--compare <list>
Example:
omniroute providers metrics
providers metric <connectionId> <metric>
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.
- 2d ago First seen · 333 lines · 36 tokens per session scan A a5c3016335aa
cli-providers is a skill published in the GitHub repository diegosouzapw/OmniRoute (59,841 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 2,029 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
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…
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…
9router-web-fetch
Fetch URL → markdown / text / HTML via 9Router /v1/web/fetch using Firecrawl / Jina Reader / Tavily Extract / Exa Contents. Use when the user wants to scrape a webpage, extract URL content, read article, or convert a URL to markdown.
9router-embeddings
Generate vector embeddings via 9Router /v1/embeddings using OpenAI / Gemini / Mistral / Voyage / Nvidia / GitHub embedding models for RAG, semantic search, similarity. Use when the user wants embeddings, vectors, RAG, semantic search, or to embed text.
9router
Entry point for 9Router — local/remote AI gateway with OpenAI-compatible REST for chat, image, TTS, embeddings, web search, web fetch. Use when the user mentions 9Router, NINEROUTERURL, or wants AI without writing provider boilerplate. This skill covers setup + indexes capability skills; fetch the relevant capability…
agent-session-monitor
Real-time agent conversation monitoring - monitors Higress access logs, aggregates conversations by session, tracks token usage. Supports web interface for viewing complete conversation history and costs. Use when users ask about current session token consumption, conversation history, or cost statistics.