Agent skill

OmniRoute Health Monitoring

by diegosouzapw in diegosouzapw/OmniRoute

Checks the health of an OmniRoute gateway: provider circuit breakers, latency percentiles, budget guard alerts, connection cooldowns and model lockouts.

MITAuto-check passedDevOps & Cloud

Install OmniRoute Health Monitoring

skills CLI

$ npx skills add diegosouzapw/OmniRoute --skill omni-resilience -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install diegosouzapw/OmniRoute omni-resilience --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omni-resilience .claude/skills/omni-resilience && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "omni-resilience" agent skill from https://github.com/diegosouzapw/OmniRoute/tree/release%2Fv3.8.52/skills/omni-resilience into .claude/skills/omni-resilience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omni-resilience", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/diegosouzapw/OmniRoute/tree/release%2Fv3.8.52/skills/omni-resilience

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add diegosouzapw/OmniRoute --skill omni-resilience -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install diegosouzapw/OmniRoute omni-resilience --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/omni-resilience .agents/skills/omni-resilience && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "omni-resilience" agent skill from https://github.com/diegosouzapw/OmniRoute/tree/release%2Fv3.8.52/skills/omni-resilience into .agents/skills/omni-resilience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omni-resilience", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add diegosouzapw/OmniRoute --skill omni-resilience -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install diegosouzapw/OmniRoute omni-resilience --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/omni-resilience .cursor/skills/omni-resilience && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "omni-resilience" agent skill from https://github.com/diegosouzapw/OmniRoute/tree/release%2Fv3.8.52/skills/omni-resilience into .cursor/skills/omni-resilience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omni-resilience", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/diegosouzapw/OmniRoute.git --path skills/omni-resilience

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add diegosouzapw/OmniRoute --skill omni-resilience -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install diegosouzapw/OmniRoute omni-resilience --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/omni-resilience .gemini/skills/omni-resilience && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "omni-resilience" agent skill from https://github.com/diegosouzapw/OmniRoute/tree/release%2Fv3.8.52/skills/omni-resilience into .gemini/skills/omni-resilience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omni-resilience", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install diegosouzapw/OmniRoute omni-resilience

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add diegosouzapw/OmniRoute --skill omni-resilience -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/omni-resilience .github/skills/omni-resilience && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "omni-resilience" agent skill from https://github.com/diegosouzapw/OmniRoute/tree/release%2Fv3.8.52/skills/omni-resilience into .github/skills/omni-resilience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omni-resilience", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add diegosouzapw/OmniRoute --skill omni-resilience -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install diegosouzapw/OmniRoute omni-resilience --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/omni-resilience .opencode/skills/omni-resilience && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "omni-resilience" agent skill from https://github.com/diegosouzapw/OmniRoute/tree/release%2Fv3.8.52/skills/omni-resilience into .opencode/skills/omni-resilience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omni-resilience", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: omni-resilience
GitHub stars: 75k
Token cost: ~1.2k tokens
SKILL.md length: 314 words
Files: 1
Skills in repo: 50
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Checks the health of an OmniRoute gateway: provider circuit breakers, latency percentiles, budget guard alerts, connection cooldowns and model lockouts.

Finding out why a provider stopped receiving traffic
SKILL.md covers Overview, Authentication, Endpoints and Payloads, plus 8 more sections
Calls curl; needs OMNIROUTE_KEY and OMNIROUTE_TOKEN
Watching p95 and p99 latency per provider

What it does

Monitoring endpoints for a running OmniRoute. The system health call returns uptime, memory, active connections, circuit breaker states, rate limit status and cache stats, and an unauthenticated quick check returns a simple ok flag. Circuit breakers keep traffic away from failing providers and are CLOSED, OPEN or HALF_OPEN, the last being a probe mode that recovers by itself.

The monitoring health response lists each provider's breaker state with a reset timestamp. A provider metrics endpoint gives p50, p95 and p99 latency, and a compression endpoint reports in-process memo statistics meant for frequent polling, with counters that reset when the process restarts.

When your agent uses it

Finding out why a provider stopped receiving traffic
Watching p95 and p99 latency per provider
Checking whether a circuit breaker is open or probing
Polling gateway health from a script

Example prompts

“Check the OmniRoute health endpoint and report any open circuit breakers.”
“What is the p95 latency for each provider on my gateway?”
“Which models are locked out right now?”

Requirements

A running OmniRoute instance
OMNIROUTE_URL and OMNIROUTE_KEY for authenticated checks

What it can do on your machine

Read from SKILL.md and the folder at commit 7510677. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- OMNIROUTE_KEY
- OMNIROUTE_TOKEN
- REQUIRE_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

OmniRoute Health Monitoring loads about 1.2k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 314 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~45
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from diegosouzapw/OmniRoute at commit 7510677, republished under its MIT licence (© diegosouzapw). 314 words, ~1,204 tokens.

Download SKILL.mdSave it as .claude/skills/omni-resilience/SKILL.md (or your agent's skills folder).

name: omni-resilience
description: Monitor provider health, circuit-breaker states, p50/p95/p99 latency metrics, and budget guard alerts. Inspect connection cooldowns and model lockouts in real time.

<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->

Overview

Monitor provider health, circuit-breaker states, p50/p95/p99 latency metrics, and budget guard alerts. Inspect connection cooldowns and model lockouts in real time.

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/monitoring/health

System health check

Returns system health including uptime, memory, circuit breakers, rate limits

bash

curl https://localhost:20128/api/monitoring/health \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/monitoring/compression

Get compression result-memo statistics

In-process compression result-memo observability snapshot — size, capacity, lifetime hits/misses/hitRate plus 1m/5m/15m/1h windowed rates. Lightweight (no DB, no provider reads) companion to GET /api/monitoring/health intended for frequent polling. Sent with Cache-Control: no-store, no-cache, must-revalidate. Counters reset on process restart.

bash

curl https://localhost:20128/api/monitoring/compression \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/provider-metrics

GET provider metrics

bash

curl https://localhost:20128/api/provider-metrics \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

Payloads

See the full OpenAPI specification at GET /api/openapi/spec or docs/openapi.yaml for detailed request/response schemas.

<!-- skill:custom-start -->

<!-- Migrated from skills/omniroute-monitoring/SKILL.md (preserved curated content) -->

OmniRoute — Monitoring & Health

Requires OMNIROUTE_URL and OMNIROUTE_KEY. See entry-point SKILL for setup.

System health

bash

curl $OMNIROUTE_URL/api/health \
  -H "Authorization: Bearer $OMNIROUTE_KEY"

Returns: uptime, memory, active connections, circuit breaker states, rate limit status, cache stats.

Unauthenticated quick check:

bash

curl $OMNIROUTE_URL/api/health
# → {"ok":true}

Provider circuit breakers

Circuit breakers prevent traffic from hitting failing providers.

States: CLOSED (normal), OPEN (blocked), HALF_OPEN (probe mode — auto-recovers).

bash

curl $OMNIROUTE_URL/api/monitoring/health \
  -H "Authorization: Bearer $OMNIROUTE_KEY"

Response includes circuitBreakers array with per-provider state and resetAt timestamp.

Per-provider metrics (p50/p95/p99)

bash

curl $OMNIROUTE_URL/api/providers/metrics \
  -H "Authorization: Bearer $OMNIROUTE_KEY"

Response shape per provider:

json

{
  "provider": "anthropic",
  "requests": 1247,
  "successRate": 0.994,
  "latency": { "p50": 820, "p95": 2100, "p99": 3800 },
  "circuitState": "CLOSED",
  "tokensUsed": 2847000
}

Via MCP (if OmniRoute is your MCP server)

omniroute_get_health            → full system health snapshot
omniroute_get_provider_metrics  → p50/p95/p99 + circuit state per provider
omniroute_get_session_snapshot  → cost, tokens, errors for current session
omniroute_check_quota           → quota balance + percent remaining + reset time
omniroute_db_health_check       → diagnose + auto-repair database drift

Quota check

bash

curl $OMNIROUTE_URL/api/quota \
  -H "Authorization: Bearer $OMNIROUTE_KEY"

Returns used/total tokens and requests per provider/account, with resetAt timestamps.

Budget guard (spend limit)

Set a session spending limit that degrades or blocks requests when hit:

bash

curl -X POST $OMNIROUTE_URL/api/budget/guard \
  -H "Authorization: Bearer $OMNIROUTE_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "limitUsd": 5.00,
    "action": "degrade",
    "degradeTo": "openai/gpt-4o-mini"
  }'

action options:

degrade — switch to a cheaper model when limit is hit
block — return 429 when limit is hit
alert — continue but add X-Budget-Warning header

MCP audit log

OmniRoute logs every MCP tool call to mcp_audit table. Query via API:

bash

curl "$OMNIROUTE_URL/api/mcp/status" \
  -H "Authorization: Bearer $OMNIROUTE_KEY"

Returns: server status, heartbeat, recent audit activity summary.

Errors

503 on health endpoint → OmniRoute is starting up; retry in 5s
Circuit breaker OPEN → provider is temporarily blocked; check resetAt to know when it auto-recovers
429 budget_exceeded → budget guard limit reached; raise limit or wait for reset

<!-- skill:custom-end -->

Files

Just SKILL.md in skills/omni-resilience of diegosouzapw/OmniRoute.

Open the folder on GitHubat commit 7510677

Compare with similar skills

OmniRoute Health Monitoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

OmniRoute Health Monitoring compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
OmniRoute Health Monitoring this skilldiegosouzapw/OmniRoute	75k	—	~1.2k	Automated safety check: Pass	MIT	today
Shopify Observabilityjeremylongshore/tons-of-skills-marketplace	2.8k	—	~1k	Automated safety check: Pass	MIT	today
OpenTelemetry Pipeline Metrics Speccomet-ml/opik	22k	—	~3.2k	Automated safety check: Pass	Apache-2.0	today
Redis Observabilityredis/agent-skills	166	2 repos	~911	Automated safety check: Pass	MIT	1 mo ago
Exploring Apm TracesPostHog/posthog	40k	—	~3.5k	Automated safety check: Pass	Custom licence	today
Logfire Instrumentationbasicmachines-co/basic-memory	4.1k	—	~2.3k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Shopify Observability
jeremylongshore/tons-of-skills-marketplace
Set up observability for Shopify app integrations with query cost tracking, rate limit monitoring, webhook delivery metrics, and structured logging.
2.8k GitHub stars~1k tokensUpdated today
DevOps & CloudAuto-check passed
OpenTelemetry Pipeline Metrics Spec
comet-ml/opik
Specifies how to instrument an opik-backend pipeline with per-stage OpenTelemetry metrics for throughput, latency, errors and queue delay by workspace.
22k GitHub stars~3.2k tokensUpdated today
DevOps & CloudAuto-check passed
Redis Observability
redis/agent-skills
Official
Redis observability guidance — which metrics to monitor (memory, connections, hit ratio, ops/sec, rejected connections), which built-in commands to reach for during incident triage (SLOWLOG, INFO…
166 GitHub starsUsed in 2 repos~911 tokens
DevOps & CloudAuto-check passed
Exploring Apm Traces
PostHog/posthog
Official
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
40k GitHub stars~3.5k tokensUpdated today
DevOps & CloudAuto-check passed
Logfire Instrumentation
basicmachines-co/basic-memory
Adds Pydantic Logfire tracing, logging and metrics to Python, JavaScript or TypeScript and Rust projects, with the correct setup order and library extras.
4.1k GitHub stars~2.3k tokensUpdated today
DevOps & CloudAuto-check passed
AWS Cost Operations
zxkane/aws-skills
AWS cost optimization, monitoring, and operational excellence expert.
367 GitHub stars~2.4k tokensUpdated 3 mo ago
DevOps & CloudAuto-check passed

Questions about OmniRoute Health Monitoring

What does OmniRoute Health Monitoring do?

Checks the health of an OmniRoute gateway: provider circuit breakers, latency percentiles, budget guard alerts, connection cooldowns and model lockouts. Monitoring endpoints for a running OmniRoute. The system health call returns uptime, memory, active connections, circuit breaker states, rate limit status and cache stats, and an unauthenticated quick check returns a simple ok flag.

When should I use OmniRoute Health Monitoring?

OmniRoute Health Monitoring fits situations like: finding out why a provider stopped receiving traffic; watching p95 and p99 latency per provider; checking whether a circuit breaker is open or probing; polling gateway health from a script.

How do I install OmniRoute Health Monitoring in Claude Code?

Run `npx skills add diegosouzapw/OmniRoute --skill omni-resilience -a claude-code`. Or copy the skill folder (skills/omni-resilience in diegosouzapw/OmniRoute) into .claude/skills/omni-resilience in your project. Claude Code loads it when a task matches its description.

How do I install OmniRoute Health Monitoring in Codex?

Run `npx skills add diegosouzapw/OmniRoute --skill omni-resilience -a codex`. Or copy the skill folder (skills/omni-resilience in diegosouzapw/OmniRoute) into .agents/skills/omni-resilience in your project. Codex loads it when a task matches its description.

Can I use OmniRoute Health Monitoring in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add diegosouzapw/OmniRoute --skill omni-resilience -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omni-resilience, .gemini/skills/omni-resilience, .github/skills/omni-resilience and .opencode/skills/omni-resilience in your project.

What does OmniRoute Health Monitoring need to run?

Going by SKILL.md and its folder, OmniRoute Health Monitoring needs the command-line tools its instructions call (curl) and credentials named OMNIROUTE_KEY, OMNIROUTE_TOKEN and REQUIRE_API_KEY. Our summary lists: A running OmniRoute instance; OMNIROUTE_URL and OMNIROUTE_KEY for authenticated checks.

Does OmniRoute Health Monitoring access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is OmniRoute Health Monitoring safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does OmniRoute Health Monitoring use?

OmniRoute Health Monitoring is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does OmniRoute Health Monitoring use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to OmniRoute Health Monitoring?

Skills that share tags, products or a category with OmniRoute Health Monitoring: Shopify Observability (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), OpenTelemetry Pipeline Metrics Spec (comet-ml/opik, 22k stars), Redis Observability (redis/agent-skills, 166 stars) and Exploring Apm Traces (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains OmniRoute Health Monitoring?

diegosouzapw (a GitHub user) maintains it in diegosouzapw/OmniRoute, which has 74,749 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 10, 2026.

Source: diegosouzapw/OmniRoute on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install OmniRoute Health Monitoring

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Overview

Authentication

Endpoints

GET /api/monitoring/health

GET /api/monitoring/compression

GET /api/provider-metrics

Payloads

OmniRoute — Monitoring & Health

System health

Provider circuit breakers

Per-provider metrics (p50/p95/p99)

Via MCP (if OmniRoute is your MCP server)

Quota check

Budget guard (spend limit)

MCP audit log

Errors

Files

Compare with similar skills

Similar skills

More from diegosouzapw/OmniRoute

Related

Questions about OmniRoute Health Monitoring