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/harness-test-writer/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/harness-test-writer)<a href="https://agentmods.dev/skills/maximhq/bifrost/harness-test-writer"><img src="https://agentmods.dev/badge/skills/maximhq/bifrost/harness-test-writer/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/harness-test-writer"><img src="https://agentmods.dev/badge/skills/maximhq/bifrost/harness-test-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00133 | $0.02271 |
| Opus 5 | $0.00067 | $0.01136 |
| Sonnet 5 | $0.00027 | $0.00454 |
| Haiku 4.5 | $0.00013 | $0.00227 |
Grade A, and why
harness-test-writer 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 10d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Provider Harness Test Writer
Turn a PR or GitHub issue into regression coverage in the provider harness: the Postman
collection at tests/e2e/api/collections/provider-harness.json, executed by newman via
make run-provider-harness-test.
This is NOT the Go test harness in core/internal/llmtests/ (that one is run via
make test-core PROVIDER=...). If the user seems to want Go-level scenario tests,
confirm before proceeding.
Step 1 - Resolve the reference
The argument may be a PR number, an issue number, or a GitHub URL.
- URL containing
/pull/=> PR. URL containing/issues/=> issue. - A bare number is ambiguous: try
gh pr view <N> --repo maximhq/bifrostfirst; if it 404s, trygh issue view <N>. If BOTH exist and refer to different things, ask the user which one they mean with AskUserQuestion. - No argument at all => ask the user for the PR/issue reference.
Fetch full context:
gh pr view <N> --repo maximhq/bifrost --json title,body,state,files,baseRefName
gh pr diff <N> --repo maximhq/bifrost
# or
gh issue view <N> --repo maximhq/bifrost --json title,body,state,labels,comments
For a PR, also note any Closes #X issue and fetch that issue too - the issue usually
contains the client-visible reproduction (exact request shapes, error bodies, status
codes) that the harness case must mirror.
Step 2 - Understand the wire-level behavior to pin
The harness tests Bifrost from the outside: HTTP requests against gateway routes, with assertions on status codes and response/SSE bodies. Translate the PR/issue into that frame:
- Which route(s)? (
/v1/chat/completions,/v1/responses, drop-ins like/openai,/anthropic,/bedrock,/genai, passthrough routes, ...) - Which provider(s) and model(s)?
- What request shape triggers the bug/feature? Reconstruct it from the issue repro or from the code path in the diff (read the changed functions and their callers).
- What is the observable failure signature before the fix (status code, error body substring) and the expected behavior after?
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.
- 10d ago First seen · 175 lines · 133 tokens per session scan A 04b488900d23
harness-test-writer is a skill published in the GitHub repository maximhq/bifrost (7,913 stars, last pushed today), licensed Apache-2.0. It adds 133 tokens to every session and 2,271 once invoked, about $0.0007 per session on Opus 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
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
connect-agent
Connect the codebase's AI agent to LangWatch agent simulations, so test suites run against the real agent process. Adds a small connect function beside the service startup that calls the agent already in the codebase, which opens an outbound connection and registers the agent with its environment and its run…
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.