Bifrost is an AI gateway that gives applications one OpenAI-compatible API for accessing models from more than 23 providers. It is used to route model requests, handle provider failover and load balancing, and apply features such as caching, guardrails, and MCP gateway support.
Borrowing it
Nothing to install: this file belongs to maximhq/bifrost. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/maximhq/bifrost/dev/.claude/skills/api-validator/SKILL.mdgit clone --depth 1 https://github.com/maximhq/bifrostWrote 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/maximhq/bifrost/api-validator)<a href="https://agentmods.dev/skills/maximhq/bifrost/api-validator"><img src="https://agentmods.dev/badge/skills/maximhq/bifrost/api-validator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/maximhq/bifrost/api-validator"><img src="https://agentmods.dev/badge/skills/maximhq/bifrost/api-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Tool Misuse · line 272 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Excessive Agency · line 583 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 671 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.1 | $0.00078 | $0.07021 |
| Opus 5.5 | $0.00031 | $0.02808 |
| Sonnet 5.5 | $0.00016 | $0.01404 |
| Haiku 4.5 | $0.00008 | $0.00702 |
Grade A, and why
api-validator 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 677 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Validator
Audit Bifrost's HTTP API surface by scanning controller/handler route registrations, deriving the actual authentication behavior from middleware wiring, and comparing the result with docs/openapi/openapi.yaml and referenced OpenAPI path files.
Use this skill when the user asks for any of the following:
- "missing APIs"
- "incorrect APIs"
- "validate APIs"
- "check OpenAPI docs against controllers"
- "include auth information"
- "fix API docs"
- "audit route coverage"
Default behavior is audit only. Do not edit files unless the user explicitly asks for fixes or approves a proposed fix plan.
Usage
/api-validator # Full audit: all handlers + OpenAPI
/api-validator management # Audit only /api/*, /health, /ws, /metrics
/api-validator inference # Audit /v1/* and provider integration APIs
/api-validator auth # Focus on effective OpenAPI security vs middleware auth
/api-validator <path-prefix> # Audit one prefix, e.g. /api/governance or /openai
/api-validator --fix # Audit, present plan, then fix after approval
If scope is unclear, ask:
Should I audit all APIs, only management APIs (/api/*), only inference/integration APIs (/v1/* and provider prefixes), or a specific path prefix?
Source of truth
Code route sources
Scan these files/directories as the controller source of truth:
| Area | Source | Notes |
|---|---|---|
| Server route wiring | transports/bifrost-http/server/server.go |
RegisterAPIRoutes, RegisterInferenceRoutes, RegisterUIRoutes, direct /metrics, middleware lists |
| HTTP handlers/controllers | transports/bifrost-http/handlers/*.go |
RegisterRoutes methods contain direct route registrations |
| SDK/provider integrations | transports/bifrost-http/integrations/*.go |
RouteConfig factories and GenericRouter.RegisterRoutes register OpenAI/Anthropic/GenAI/Bedrock/Cohere/LiteLLM/LangChain/PydanticAI/Cursor/Passthrough routes |
| Auth middleware | transports/bifrost-http/handlers/middlewares.go |
APIMiddleware, InferenceMiddleware, whitelists, realtime auth skips |
| Context auth extraction | transports/bifrost-http/lib/ctx.go |
Virtual key and API key header extraction |
| Governance VK parser | plugins/governance/utils.go |
Accepted virtual key headers for VK self-service endpoints |
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.
- 1mo ago First seen · 677 lines · 78 tokens per session scan A d4287deaa8bf
api-validator is a skill published in the GitHub repository maximhq/bifrost (8,898 stars, last pushed yesterday), licensed Apache-2.0. It adds 78 tokens to every session and 7,021 once invoked, about $0.0003 per session on Opus 5.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
omni-inference
The core OpenAI-compatible inference endpoints: chat completions, embeddings, images, audio (TTS/STT), moderations, rerank, and the Responses API. The primary integration surface for AI agents.
omni-providers
Manage provider connections, API keys, OAuth flows, and connection tests via the REST API. List, add, update, remove, and test AI provider integrations across OmniRoute's 374-provider catalog.
omni-auth
Manage API key authentication and session tokens. Start here to authenticate requests via Bearer token, obtain session cookies, and configure login requirements for the OmniRoute API.
omni-combos-routing
Create and manage routing combos with 19 strategies (priority, weighted, round-robin, Auto-combo, and more). Configure fallback chains, test routing outcomes, and retrieve combo metrics.
omni-api-keys
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.
omni-mcp
Connect to the OmniRoute MCP server (110 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 33 permission scopes.