Agent skill

OmniRoute Usage Logs

by diegosouzapw in diegosouzapw/OmniRoute

Queries OmniRoute call logs, usage history and analytics, filters them by provider, model, status or cost, and reads or sets usage budgets.

MITAuto-check passedData & Analytics

Install OmniRoute Usage Logs

skills CLI
$ npx skills add diegosouzapw/OmniRoute --skill omni-usage-logs -a claude-code

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

GitHub CLI
$ gh skill install diegosouzapw/OmniRoute omni-usage-logs --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-usage-logs .claude/skills/omni-usage-logs && 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/

Facts

Skill name
omni-usage-logs
GitHub stars
74k
Used in
1 other repo
Token cost
~2k tokens
SKILL.md length
440 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Queries OmniRoute call logs, usage history and analytics, filters them by provider, model, status or cost, and reads or sets usage budgets.

  • Finding which provider or model drives most of your spend
  • SKILL.md covers Overview, Authentication and Endpoints
  • Calls curl; needs OMNIROUTE_TOKEN and REQUIRE_API_KEY
  • Looking up the call log for a failed request

What it does

The reporting side of an OmniRoute gateway. Endpoints return usage analytics, call logs, request logs, proxy logs and a usage history, and one returns usage for a specific connection. A filters endpoint lists the distinct providers, models, accounts and API keys seen in call logs, which feeds the dropdowns of the Logs tab.

Individual call logs can be fetched by id. Budget endpoints return current limits and consumption and let you set or update the limits used for tracking. The description also covers exporting logs and aggregating token usage across connections. A Bearer token or session cookie is required.

When your agent uses it

  • Finding which provider or model drives most of your spend
  • Looking up the call log for a failed request
  • Setting a usage budget on the gateway
  • Aggregating token usage per connection

Example prompts

  • “Pull OmniRoute usage analytics grouped by provider for this week.”
  • “Fetch the call log for my most recent failed request.”
  • “Set a usage budget on my gateway and report consumption so far.”

Requirements

  • A running OmniRoute instance
  • A Bearer token or session cookie

What it can do on your machine

Read from SKILL.md and the folder at commit 8ad6b1c. 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_TOKEN
    • REQUIRE_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

OmniRoute Usage Logs loads about 2k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 440 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
~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 8ad6b1c, republished under its MIT licence (© diegosouzapw). 440 words, ~2,023 tokens.

Download SKILL.mdSave it as .claude/skills/omni-usage-logs/SKILL.md (or your agent's skills folder).
name
omni-usage-logs
description
Access detailed call logs and usage analytics. Filter by provider, model, time range, status, and cost. Export logs and aggregate token usage across all connections.
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->

Overview

Access detailed call logs and usage analytics. Filter by provider, model, time range, status, and cost. Export logs and aggregate token usage across all connections.

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/usage/analytics

Get usage analytics

bash
curl https://localhost:20128/api/usage/analytics \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/call-logs

Get call logs

bash
curl https://localhost:20128/api/usage/call-logs \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/call-logs/filters

Get call log filter options

Distinct providers, models, accounts and API keys seen in call logs, plus every configured API key (id and name only). Feeds the Logs tab filter dropdowns.

bash
curl https://localhost:20128/api/usage/call-logs/filters \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/call-logs/{id}

Get a specific call log

bash
curl https://localhost:20128/api/usage/call-logs/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/{connectionId}

Get usage for a specific connection

bash
curl https://localhost:20128/api/usage/{connectionId} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/history

Get usage history

bash
curl https://localhost:20128/api/usage/history \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/logs

Get usage logs

bash
curl https://localhost:20128/api/usage/logs \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/proxy-logs

Get proxy logs

bash
curl https://localhost:20128/api/usage/proxy-logs \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/request-logs

Get request logs

bash
curl https://localhost:20128/api/usage/request-logs \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/budget

Get usage budget status

Returns current budget limits and consumption.

bash
curl https://localhost:20128/api/usage/budget \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
POST /api/usage/budget

Configure usage budget

Set or update budget limits for usage tracking.

bash
curl -X POST https://localhost:20128/api/usage/budget \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
GET /api/usage/cache-health

Get prompt-cache health summary

Summarizes the write/read cache ratio from call_logs for a time window: distribution (p50/p90/p99/max of cache-write tokens), warm/cold/rewrite/uncached call counts, the "heavy write" outlier share (10x the window median, floored at 1024 tokens — Anthropic's cache-creation minimum), and a per-model breakdown. Only successful (status = 200) calls with a non-null cache column are counted.

bash
curl https://localhost:20128/api/usage/cache-health \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/model-latency-stats

Get per-model/provider latency statistics

Aggregates usage_history rows into per-(provider, model) latency stats (avg/p50/p95/p99, std-dev, TTFT, tokens/sec) over a rolling window. Falls back from successful-only to all-sample rows when the successful count is below minSamples.

bash
curl https://localhost:20128/api/usage/model-latency-stats \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/budget/bulk

GET usage › budget › bulk

bash
curl https://localhost:20128/api/usage/budget/bulk \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/codex-reset-credit

GET usage › codex reset credit

bash
curl https://localhost:20128/api/usage/codex-reset-credit \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
Show full SKILL.md (181 more words)Show less
POST /api/usage/codex-reset-credit

POST usage › codex reset credit

bash
curl -X POST https://localhost:20128/api/usage/codex-reset-credit \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
GET /api/usage/combo-forecast

GET usage › combo forecast

bash
curl https://localhost:20128/api/usage/combo-forecast \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/combo-health

GET usage › combo health

bash
curl https://localhost:20128/api/usage/combo-health \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/combo-health-autopilot

GET usage › combo health autopilot

bash
curl https://localhost:20128/api/usage/combo-health-autopilot \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/combo-health-dashboard

GET usage › combo health dashboard

bash
curl https://localhost:20128/api/usage/combo-health-dashboard \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/combo-scoring-inspector

GET usage › combo scoring inspector

bash
curl https://localhost:20128/api/usage/combo-scoring-inspector \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/combo-trace/{id}

GET usage › combo trace › <id>

bash
curl https://localhost:20128/api/usage/combo-trace/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/om-usage

GET usage › om usage

bash
curl https://localhost:20128/api/usage/om-usage \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/provider-limits

GET usage › provider limits

bash
curl https://localhost:20128/api/usage/provider-limits \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
POST /api/usage/provider-limits

POST usage › provider limits

bash
curl -X POST https://localhost:20128/api/usage/provider-limits \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
GET /api/usage/provider-window-costs

GET usage › provider window costs

bash
curl https://localhost:20128/api/usage/provider-window-costs \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/quota

GET usage › quota

bash
curl https://localhost:20128/api/usage/quota \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/requests-by-provider-date

GET usage › requests by provider date

bash
curl https://localhost:20128/api/usage/requests-by-provider-date \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/route-explain/{id}

GET usage › route explain › <id>

bash
curl https://localhost:20128/api/usage/route-explain/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/token-limits

GET usage › token limits

bash
curl https://localhost:20128/api/usage/token-limits \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
POST /api/usage/token-limits

POST usage › token limits

Save a per-key token limit. A key holds one limit per scope and reset interval, so daily, weekly and monthly limits for the same scope coexist. Without id, a new limit is added (or the key's limit for the same scope and interval is updated); with id, that limit is updated.

bash
curl -X POST https://localhost:20128/api/usage/token-limits \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
DELETE /api/usage/token-limits

DELETE usage › token limits

bash
curl -X DELETE https://localhost:20128/api/usage/token-limits \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/usage/utilization

GET usage › utilization

bash
curl https://localhost:20128/api/usage/utilization \
  -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.

© diegosouzapw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

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

Open the folder on GitHubat commit 8ad6b1c

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in diegosouzapw/OmniRoute, which our catalogue first saw on October 7, 2026.

Compare with similar skills

OmniRoute Usage Logs 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 Usage Logs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
OmniRoute Usage Logs this skilldiegosouzapw/OmniRoute74k1 repos~2kAutomated safety check: PassMIT
Sentry Instrumentgetsentry/sentry-for-ai268—~3.2kAutomated safety check: PassApache-2.0
Caveman Workflow LabelerJuliusBrussee/caveman110k1 repos~1.3kAutomated safety check: PassApache-2.0
Caveman Evidence ReviewJuliusBrussee/caveman110k1 repos~927Automated safety check: PassApache-2.0
CodexBar Usage Readersteipete/CodexBar22k—~320Automated safety check: PassMIT
Caveman Gateway SetupJuliusBrussee/caveman110k1 repos~2.6kAutomated safety check: WarnApache-2.0

Similar skills

  • Sentry Instrument

    getsentry/sentry-for-ai

    Official

    Instrument an application with Sentry — detect the platform, install and initialize the SDK if needed, and wire up any signal — error monitoring, tracing/performance, logging, metrics, profiling…

    268 GitHub stars~3.2k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Caveman Workflow Labeler

    JuliusBrussee/caveman

    Finds every LLM workflow in a repository, proposes a labeling table and, once you agree, wires labels so Caveman Cloud groups spend per workflow.

    110k GitHub starsUsed in 1 repo~1.3k tokens
    AI & LLM EngineeringAuto-check passed
  • Caveman Evidence Review

    JuliusBrussee/caveman

    Read-only review of Caveman Cloud data to explain where LLM spend goes: cost, score, workflows, traces, latency, errors, routing and verified savings.

    110k GitHub starsUsed in 1 repo~927 tokens
    AI & LLM EngineeringAuto-check passed
  • CodexBar Usage Reader

    steipete/CodexBar

    CodexBar read. Provider usage, limits, credits, config health. JSON. No writes.

    22k GitHub stars~320 tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Caveman Gateway Setup

    JuliusBrussee/caveman

    Routes every LLM call in a repository through the Caveman Cloud gateway in record mode, so requests and costs are measured without changing behavior.

    110k GitHub starsUsed in 1 repo~2.6k tokens
    DevOps & CloudAuto-check: warnings
  • CCC Token Throughput

    amirfish1/claude-command-center

    Answers token usage and cost questions from the Claude Command Center throughput dashboard and shares its link, for the last 7 days or one session.

    177 GitHub stars~676 tokensUpdated today
    Productivity & AutomationAuto-check passed

More from diegosouzapw/OmniRoute

All 50 skills in this repo
  • OmniRoute Backup and Sync CLI

    diegosouzapw/OmniRoute

    Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.

    74k GitHub stars~948 tokensUpdated today
    Auto-check passed
  • OmniRoute Settings API

    diegosouzapw/OmniRoute

    Read and update global application settings: system prompts, thinking budget, IP filters, payload rules, combo defaults, and require-login configuration.

    74k GitHub starsUsed in 1 repo~3.6k tokens
    Auto-check passed
  • Quality Scan

    diegosouzapw/OmniRoute

    Runs a scoped, read-only quality scan on a repository candidate and reports exact evidence, failures and frozen debt, without treating a static scan as release acceptance.

    74k GitHub stars~748 tokensUpdated today
    Auto-check passed
  • OmniRoute Database Backups

    diegosouzapw/OmniRoute

    Trigger system backups, restore from backup files, and manage the SQLite database lifecycle. Supports export, import, and incremental snapshot strategies.

    74k GitHub starsUsed in 1 repo~395 tokens
    Auto-check passed
  • OmniRoute Provider Management

    diegosouzapw/OmniRoute

    Manages AI provider connections, API keys, OAuth flows and connection tests through OmniRoute's REST API across its 327-provider catalog.

    74k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • OmniRoute LLM Cache

    diegosouzapw/OmniRoute

    Documents OmniRoute's cache endpoints for reading cache statistics and clearing entries, statistics or the reasoning cache, with notes on TTL and similarity settings.

    74k GitHub starsUsed in 1 repo~529 tokens
    Auto-check passed

Questions about OmniRoute Usage Logs

What does OmniRoute Usage Logs do?

Queries OmniRoute call logs, usage history and analytics, filters them by provider, model, status or cost, and reads or sets usage budgets. The reporting side of an OmniRoute gateway. Endpoints return usage analytics, call logs, request logs, proxy logs and a usage history, and one returns usage for a specific connection.

When should I use OmniRoute Usage Logs?

OmniRoute Usage Logs fits situations like: finding which provider or model drives most of your spend; looking up the call log for a failed request; setting a usage budget on the gateway; aggregating token usage per connection.

How do I install OmniRoute Usage Logs in Claude Code?

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

How do I install OmniRoute Usage Logs in Codex?

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

Can I use OmniRoute Usage Logs 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-usage-logs -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-usage-logs, .gemini/skills/omni-usage-logs, .github/skills/omni-usage-logs and .opencode/skills/omni-usage-logs in your project.

What does OmniRoute Usage Logs need to run?

Going by SKILL.md and its folder, OmniRoute Usage Logs needs the command-line tools its instructions call (curl) and credentials named OMNIROUTE_TOKEN and REQUIRE_API_KEY. Our summary lists: A running OmniRoute instance; A Bearer token or session cookie.

Does OmniRoute Usage Logs 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 Usage Logs 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 Usage Logs use?

OmniRoute Usage Logs 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 Usage Logs use?

About 2k tokens (SKILL.md is roughly 8.1k 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 Usage Logs?

Skills that share tags, products or a category with OmniRoute Usage Logs: Sentry Instrument (getsentry/sentry-for-ai, 268 stars), Caveman Workflow Labeler (JuliusBrussee/caveman, 110k stars), Caveman Evidence Review (JuliusBrussee/caveman, 110k stars) and CodexBar Usage Reader (steipete/CodexBar, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains OmniRoute Usage Logs?

diegosouzapw (a GitHub user) maintains it in diegosouzapw/OmniRoute, which has 73,701 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 6, 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.