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/nexenio/bifrost-plugin/bifrost-code-modenpx skills add neXenio/bifrost-plugin --skill bifrost-code-modegit clone --depth 1 https://github.com/neXenio/bifrost-pluginWrote 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/nexenio/bifrost-plugin/bifrost-code-mode)<a href="https://agentmods.dev/skills/nexenio/bifrost-plugin/bifrost-code-mode"><img src="https://agentmods.dev/badge/skills/nexenio/bifrost-plugin/bifrost-code-mode.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.00112 | $0.01423 |
| Opus 5 | $0.00056 | $0.00711 |
| Sonnet 5 | $0.00022 | $0.00285 |
| Haiku 4.5 | $0.00011 | $0.00142 |
Grade A, and why
bifrost-code-mode 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 3d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bifrost code mode
Most servers on a Bifrost gateway are not flat tools. They do not appear in your
tool list and mcp__bifrost__<server>-<tool> does not exist for them. They are reached
by writing a short Starlark snippet and running it with executeToolCode.
If a capability seems missing, it is almost certainly here. Do not conclude the gateway lacks it, and do not fall back to guessing from training data, until you have checked.
The four meta-tools
Exact schemas, as the gateway advertises them:
| Tool | Parameters | Required |
|---|---|---|
listToolFiles |
(none) | — |
readToolFile |
fileName, startLine, endLine |
fileName |
getToolDocs |
server, tool |
both |
executeToolCode |
code |
code |
The parameter is fileName, not path or file. Passing path fails with
fileName parameter is required and must be a string.
fileName is the full catalog path: servers/<server>/<tool>.pyi.
Workflow
1. Discover. listToolFiles() returns the catalog, grouped by server:
servers/
jira/
search_jira_tickets.pyi
create_jira_ticket.pyi
...
2. Confirm the signature. Never call a tool whose parameters you have not read.
readToolFile(fileName="servers/jira/search_jira_tickets.pyi")
returns a typed stub with the exact callable name and an inline description:
# Total lines: 10 (this is the complete file, no need to paginate)
# jira.search_jira_tickets tool
# Usage: jira.tool_name(param=value)
def search_jira_tickets(query: str, max_results: float = None, service: str = None, status: str = None) -> dict: # Search JIRA before filing a new ticket to avoid duplicates.
The def name is the exact callable. Descriptions in .pyi files may be truncated —
use getToolDocs(server="jira", tool="search_jira_tickets") when a parameter's meaning
or return shape is unclear.
A wrong tool name is cheap to recover from: the error lists every valid tool on that server.
3. Execute.
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.
- 3d ago First seen · 152 lines · 112 tokens per session scan A 1e4f9e20b46e
bifrost-code-mode is a skill published in the GitHub repository neXenio/bifrost-plugin (2 stars, last pushed 15d ago), licensed MIT. It adds 112 tokens to every session and 1,423 once invoked, about $0.0006 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-31.
Other skills, from other repositories
omni-cli-tools
Manage CLI tool integrations exposed via the API. List, configure, and invoke CLI tool plugins that extend OmniRoute's automation surface.
cli-providers
Manage provider connections from the CLI: list available/configured providers, add, test, test-all, validate, rotate API keys, and view per-provider metrics.
omni-compression
Configure RTK (command output), Caveman (prose), and stacked compression modes. Manage language packs, custom rules, and test prompt compression reducing tokens by 60–90%.
cli-eval
Create and run evaluation suites, watch live benchmark progress, view scorecards, compare model performance, and integrate eval runs with CI workflows from the CLI.
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.
cli-backup-sync
Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.