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.
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/maximhq/bifrost/docs-writernpx skills add maximhq/bifrost --skill docs-writergit 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/docs-writer)<a href="https://agentmods.dev/skills/maximhq/bifrost/docs-writer"><img src="https://agentmods.dev/badge/skills/maximhq/bifrost/docs-writer.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00083 | $0.07984 |
| Opus 5 | $0.00042 | $0.03992 |
| Sonnet 5 | $0.00017 | $0.01597 |
| Haiku 4.5 | $0.00008 | $0.00798 |
Grade A, and why
docs-writer scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- API examples with curl commands How it starts
The opening of the file, as written. The whole thing — 861 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bifrost Documentation Writer
Write, update, and review Mintlify MDX documentation for Bifrost features. Performs thorough codebase research across both the React UI and Go backend, validates config.json examples against the schema, and follows established documentation conventions.
Usage
/docs-writer <feature-name> # Write new docs for a feature
/docs-writer update <doc-path> # Update an existing doc page
/docs-writer review <doc-path> # Review a doc for accuracy and completeness
Workflow Overview
- Understand the request -- Determine which feature needs documentation
- Research the codebase -- Explore UI pages, Go handlers, config schema, and existing docs
- Research external context -- Use Context7 and WebSearch for additional information
- Ask clarifying questions -- Confirm scope, audience, and edge cases with the user
- Present doc outline -- Show a structured outline and wait for approval
- Write the documentation -- Create the MDX file following Mintlify conventions
- Update navigation -- Add the new page to docs.json
- Present for review -- Show the complete doc and incorporate feedback
Step 1: Understand the Request
For new docs (/docs-writer <feature-name>)
Parse the feature name and map it to codebase areas. Common feature-to-directory mappings:
| Feature Name | UI Directory | Handler File | Config Schema Section | Existing Docs |
|---|---|---|---|---|
| virtual-keys | ui/app/workspace/virtual-keys/ |
handlers/governance.go |
governance.virtual_keys |
docs/features/governance/virtual-keys.mdx |
| routing | ui/app/workspace/routing-rules/ |
handlers/governance.go |
governance.routing_rules |
docs/features/governance/routing.mdx |
| providers | ui/app/workspace/providers/ |
handlers/providers.go |
providers |
docs/providers/ |
| mcp | ui/app/workspace/mcp-registry/ |
handlers/mcp.go |
mcp |
docs/mcp/ |
| plugins | ui/app/workspace/plugins/ |
handlers/plugins.go |
plugins |
docs/features/plugins/ |
| logs / observability | ui/app/workspace/logs/ |
handlers/logging.go |
client.enable_logging |
docs/features/observability/ |
| semantic-caching | ui/app/workspace/config/caching/ |
handlers/cache.go |
plugins.semantic_cache + vector_store |
docs/features/semantic-caching.mdx |
| guardrails | ui/app/workspace/guardrails/ |
Enterprise | guardrails_config |
docs/enterprise/guardrails.mdx |
| clustering | ui/app/workspace/cluster/ |
Enterprise | cluster_config |
docs/enterprise/clustering.mdx |
| load-balancing | ui/app/workspace/adaptive-routing/ |
Enterprise | load_balancer_config |
docs/enterprise/adaptive-load-balancing.mdx |
| audit-logs | ui/app/workspace/audit-logs/ |
Enterprise | audit_logs |
docs/enterprise/audit-logs.mdx |
| rbac | ui/app/workspace/rbac/ |
Enterprise | auth_config |
docs/enterprise/rbac.mdx |
| config | ui/app/workspace/config/ |
handlers/config.go |
client |
docs/quickstart/ |
| budget-and-limits | ui/app/workspace/virtual-keys/ |
handlers/governance.go |
governance.budgets, governance.rate_limits |
docs/features/governance/budget-and-limits.mdx |
| mcp-tools | ui/app/workspace/mcp-tool-groups/ |
handlers/governance.go |
governance.virtual_keys[].mcp_configs |
docs/features/governance/mcp-tools.mdx |
| fallbacks | N/A (request-level) | handlers/inference.go |
N/A | docs/features/fallbacks.mdx |
| telemetry | ui/app/workspace/observability/ |
handlers/plugins.go |
plugins.prometheus, plugins.otel |
docs/features/telemetry.mdx |
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.
- 5d ago First seen · 861 lines · 83 tokens per session scan A 1d9d08c32907
docs-writer is a skill published in the GitHub repository maximhq/bifrost (7,809 stars, last pushed today), licensed Apache-2.0. It adds 83 tokens to every session and 7,984 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
documentation-lookup
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.
develop-ownplanner-feature
Plan, review, implement, and verify an OwnPlanner feature or use case from a GitHub issue, issue URL, repository plan, or direct feature request. Use for new product behavior and cross-layer enhancements that may affect Domain, Application, Infrastructure, Web API, MCP, console/stdio, React frontend, tests…
release-alignment
Use this skill for MCPMate pre-release or post-release documentation alignment, including GitHub Release Notes, website changelog entries, README release-facing copy, roadmap positioning, localized website docs, and release-description/changelog consistency checks.
uat-acceptance
Use this skill for MCPMate UI/UX review, UAT planning, Playwright acceptance, Admin Console acceptance, Board acceptance, Extension delivery acceptance, or any request to judge whether a page, flow, component, PR, or deliverable conforms to MCPMate product taste and acceptance standards. Use it even when the user does…
project-flow
Use this skill whenever work needs to be aligned with the MCPMate GitHub Project, including roadmap slicing, draft-item planning, PR scoping, worktree setup, or task-status updates. Trigger on requests about planning, roadmap, project board, task center, worktree discipline, or how to split work into reviewable slices.
review-flow
Use this skill whenever MCPMate work needs code review, PR readiness checks, severity calibration, or final findings ordering. Trigger on review requests, merge-readiness checks, PR cleanup, risk discussion, or any request to assess whether a change is ready to land.