New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

OmniRoute API Keys

by diegosouzapw in diegosouzapw/OmniRoute

Documents the OmniRoute REST endpoints for creating, listing, updating, regenerating and deleting API keys, with per-key scopes, spending limits, expiry and device lists.

MITAuto-check passedBackend & APIs

Install OmniRoute API Keys

skills CLI
$ npx skills add diegosouzapw/OmniRoute --skill omni-api-keys -a claude-code

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

GitHub CLI
$ gh skill install diegosouzapw/OmniRoute omni-api-keys --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-api-keys .claude/skills/omni-api-keys && 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-api-keys
GitHub stars
74k
Token cost
~1.2k tokens
SKILL.md length
217 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Documents the OmniRoute REST endpoints for creating, listing, updating, regenerating and deleting API keys, with per-key scopes, spending limits, expiry and device lists.

  • Creating a new OmniRoute API key with a spending limit and expiry
  • SKILL.md covers Overview, Authentication, Endpoints and Payloads
  • Calls curl; needs OMNIROUTE_TOKEN and REQUIRE_API_KEY
  • Rotating or revoking a key that may have leaked

What it does

API keys gate access to all proxy and management endpoints, and this skill covers the key lifecycle. Endpoints list and create keys, get, update and delete one by ID, regenerate or reveal a key, read its usage limits and list the devices seen using it. Device tracking stores masked IPs and User-Agent fingerprints in memory, and IPs are masked before storage. Key groups have their own list and create endpoints, and the description says keys carry scopes, spending limits and expiration.

Calls need a Bearer token or session cookie, obtained from POST /api/auth/login, or REQUIRE_API_KEY set to false during local development. Each endpoint is shown as a curl command against a local server, and the full request and response schemas are in the OpenAPI spec at /api/openapi/spec.

When your agent uses it

  • Creating a new OmniRoute API key with a spending limit and expiry
  • Rotating or revoking a key that may have leaked
  • Checking which devices have used a particular key
  • Reading a key's usage limits or organizing keys into groups

Example prompts

  • “Create an OmniRoute API key for the staging team with a monthly spending limit.”
  • “Regenerate the key for the build server and tell me what else needs updating.”
  • “List the devices that have used my OmniRoute key this week.”

Requirements

  • A running OmniRoute server and a Bearer token or session cookie

What it can do on your machine

Read from SKILL.md and the folder at commit f8a8131. 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 API Keys loads about 1.2k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 217 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 f8a8131, republished under its MIT licence (© diegosouzapw). 217 words, ~1,220 tokens.

Download SKILL.mdSave it as .claude/skills/omni-api-keys/SKILL.md (or your agent's skills folder).
name
omni-api-keys
description
Create, list, rotate, and revoke OmniRoute API keys. Control per-key scopes, spending limits, and expiration. Keys gate access to all proxy and management endpoints.
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->

Overview

Create, list, rotate, and revoke OmniRoute API keys. Control per-key scopes, spending limits, and expiration. Keys gate access to all proxy and management endpoints.

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/keys

List API keys

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

Create API key

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

Get API key

bash
curl https://localhost:20128/api/keys/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
PATCH /api/keys/{id}

Update API key

bash
curl -X PATCH https://localhost:20128/api/keys/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
DELETE /api/keys/{id}

Delete API key

bash
curl -X DELETE https://localhost:20128/api/keys/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/keys/{id}/devices

List devices for an API key

Lists the distinct devices (masked IP + User-Agent fingerprints) tracked for an API key by the in-memory device tracker. IPs are masked before storage; the route never sees the raw client IP.

bash
curl https://localhost:20128/api/keys/{id}/devices \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
POST /api/keys/{id}/regenerate

POST keys › <id> › regenerate

bash
curl -X POST https://localhost:20128/api/keys/{id}/regenerate \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
GET /api/keys/{id}/reveal

GET keys › <id> › reveal

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

GET keys › <id> › usage limits

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

GET keys › groups

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

POST keys › groups

bash
curl -X POST https://localhost:20128/api/keys/groups \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
GET /api/keys/groups/{id}

GET keys › groups › <id>

bash
curl https://localhost:20128/api/keys/groups/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
PUT /api/keys/groups/{id}

PUT keys › groups › <id>

bash
curl -X PUT https://localhost:20128/api/keys/groups/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
DELETE /api/keys/groups/{id}

DELETE keys › groups › <id>

bash
curl -X DELETE https://localhost:20128/api/keys/groups/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/keys/groups/{id}/keys

GET keys › groups › <id> › keys

bash
curl https://localhost:20128/api/keys/groups/{id}/keys \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
POST /api/keys/groups/{id}/keys

POST keys › groups › <id> › keys

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

DELETE keys › groups › <id> › keys

bash
curl -X DELETE https://localhost:20128/api/keys/groups/{id}/keys \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
GET /api/keys/groups/{id}/permissions

GET keys › groups › <id> › permissions

bash
curl https://localhost:20128/api/keys/groups/{id}/permissions \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
POST /api/keys/groups/{id}/permissions

POST keys › groups › <id> › permissions

bash
curl -X POST https://localhost:20128/api/keys/groups/{id}/permissions \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
DELETE /api/keys/groups/{id}/permissions

DELETE keys › groups › <id> › permissions

bash
curl -X DELETE https://localhost:20128/api/keys/groups/{id}/permissions \
  -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-api-keys of diegosouzapw/OmniRoute.

Open the folder on GitHubat commit f8a8131

Compare with similar skills

OmniRoute API Keys 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 API Keys compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
OmniRoute API Keys this skilldiegosouzapw/OmniRoute74k—~1.2kAutomated safety check: PassMIT
Auth BypassNeoTheCapt/RedteamAgent142—~1.3kAutomated safety check: PassNone
Cb Security HardeningBlkLeg/CircuitBreaker201—~2.1kAutomated safety check: PassMIT
API Security Designvinayaklatthe/microsoft-security-skills175—~2.2kAutomated safety check: PassMIT
Django Securityaffaan-m/ECC275k1 repos~4.3kAutomated safety check: NotesMIT
Security ProtocolNoobyGains/godmode107—~2.4kAutomated safety check: NotesMIT

Similar skills

  • Auth Bypass

    NeoTheCapt/RedteamAgent

    Test for authentication and authorization flaws including credential attacks, session issues, and access control bypasses

    142 GitHub stars~1.3k tokensUpdated 2 mo ago
    Backend & APIsAuto-check passed

  • Cb Security Hardening

    BlkLeg/CircuitBreaker

    Enforces Circuit Breaker security hardening conventions across backend, frontend, Docker, and nginx.

    201 GitHub stars~2.1k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed

  • API Security Design

    vinayaklatthe/microsoft-security-skills

    Guidance for designing secure APIs on Azure - authentication, authorization, gateway controls, input validation, rate limiting, secret management, and runtime threat detection - aligned to OWASP API…

    175 GitHub stars~2.2k tokensUpdated 3 mo ago
    Backend & APIsAuto-check passed

  • Django Security

    affaan-m/ECC

    Django security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.

    275k GitHub starsUsed in 1 repo~4.3k tokens
    Backend & APIsAuto-check: notes

  • Security Protocol

    NoobyGains/godmode

    A skill your agent uses when writing code that processes user input, manages authentication or authorization, constructs database queries, handles file operations, interacts with external data…

    107 GitHub stars~2.4k tokensUpdated 7 mo ago
    Backend & APIsAuto-check: notes

  • Security

    oliver-kriska/claude-elixir-phoenix

    Build and harden Phoenix auth and security — OAuth login, password hashing, sessions, RBAC, rate limiting, CSRF, XSS, SQL injection, secrets.

    565 GitHub stars~1k tokensUpdated 2 days ago
    Backend & APIsAuto-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 Prompt Compression CLI

    diegosouzapw/OmniRoute

    Configure and test prompt compression from the CLI. Manage RTK filters, Caveman rules, stacked compression modes, and preview compression output with real…

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

Categories

Questions about OmniRoute API Keys

What does OmniRoute API Keys do?

Documents the OmniRoute REST endpoints for creating, listing, updating, regenerating and deleting API keys, with per-key scopes, spending limits, expiry and device lists. API keys gate access to all proxy and management endpoints, and this skill covers the key lifecycle. Endpoints list and create keys, get, update and delete one by ID, regenerate or reveal a key, read its usage limits and list the devices seen using it.

When should I use OmniRoute API Keys?

OmniRoute API Keys fits situations like: creating a new OmniRoute API key with a spending limit and expiry; rotating or revoking a key that may have leaked; checking which devices have used a particular key; reading a key's usage limits or organizing keys into groups.

How do I install OmniRoute API Keys in Claude Code?

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

How do I install OmniRoute API Keys in Codex?

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

Can I use OmniRoute API Keys 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-api-keys -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-api-keys, .gemini/skills/omni-api-keys, .github/skills/omni-api-keys and .opencode/skills/omni-api-keys in your project.

What does OmniRoute API Keys need to run?

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

Does OmniRoute API Keys 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 API Keys 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 API Keys use?

OmniRoute API Keys 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 API Keys use?

About 1.2k tokens (SKILL.md is roughly 4.9k 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 API Keys?

Skills that share tags, products or a category with OmniRoute API Keys: Auth Bypass (NeoTheCapt/RedteamAgent, 142 stars), Cb Security Hardening (BlkLeg/CircuitBreaker, 201 stars), API Security Design (vinayaklatthe/microsoft-security-skills, 175 stars) and Django Security (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains OmniRoute API Keys?

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