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/e2e-testnpx skills add maximhq/bifrost --skill e2e-testgit 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/e2e-test)<a href="https://agentmods.dev/skills/maximhq/bifrost/e2e-test"><img src="https://agentmods.dev/badge/skills/maximhq/bifrost/e2e-test.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.00000 | $0.08525 |
| Opus 5 | $0.00000 | $0.04262 |
| Sonnet 5 | $0.00000 | $0.01705 |
| Haiku 4.5 | $0.00000 | $0.00852 |
Grade A, and why
e2e-test 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 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.
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 — 951 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: e2e-test description: Write, run, debug, audit, and auto-update Playwright E2E tests for the Bifrost UI. Use when asked to create new E2E tests, add test coverage, fix flaky tests, debug failing tests, audit test correctness, update tests after UI changes, or sync tests with modified components. Invoked with /e2e-test <FEATURE_NAME>, /e2e-test fix <SPEC_FILE>, /e2e-test sync, or /e2e-test audit. allowed-tools: Read, Grep, Glob, Bash, Edit, Write, Task, AskUserQuestion, TodoWrite
Playwright E2E Testing
Write, run, debug, and auto-update Playwright E2E tests following Bifrost's established patterns and conventions. Automatically detects UI changes and updates affected tests.
Usage
/e2e-test <FEATURE_NAME> # Create or update tests for a feature
/e2e-test fix <SPEC_FILE> # Debug and fix a failing test
/e2e-test run <FEATURE_NAME> # Run tests for a specific feature
/e2e-test run # Run all E2E tests
/e2e-test sync # Detect UI changes and update affected tests
/e2e-test sync <FEATURE_NAME> # Sync tests for a specific feature with UI changes
/e2e-test audit # Audit all specs for incorrect/weak assertions
/e2e-test audit <FEATURE_NAME> # Audit a specific feature's specs
Workflow Overview
- Understand the feature - Read the UI code to understand what needs testing
- Check existing tests - Review existing test patterns for the feature or similar features
- Identify data-testid attributes - Find selectors in the UI code
- Write/update tests - Follow the established patterns (page objects, data factories, fixtures)
- Run the tests - Execute and verify they pass
- Fix failures - Debug and fix any issues
Auto-Update Workflow (sync mode)
When invoked with sync, or when UI changes are detected, automatically update E2E tests:
Step 0: Detect What Changed
Detect UI changes by checking git diff against the base branch:
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 · 951 lines · 0 tokens per session scan A d8fecf041fcc
e2e-test is a skill published in the GitHub repository maximhq/bifrost (7,809 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 8,525 tokens. 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
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…
visual-check
Record and check iOS and Android UI flows with uiagent.py (cloud) or uiagentlocal.py (Ollama). Use when recording a visual baseline, running check or check-all, debugging simulator taps, or editing files under visual-testing/.
testing-api-assertions
Verify API requests in tests. Use when testing that correct API calls are made for create, update, or delete operations. Use when testing mutations, form submissions, or actions with backend side effects.
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.
ui-preview
Capture headless-Chrome screenshots of the tingly-box frontend (running locally in mock mode) so frontend changes can be visually verified in environments without a real browser. Use when the user asks to "preview", "screenshot", "see the page", "show me the UI", "verify visually", or when frontend layout / component…
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…