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.
git 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/commands/nexenio/bifrost-plugin/bifrost-debug)<a href="https://agentmods.dev/commands/nexenio/bifrost-plugin/bifrost-debug"><img src="https://agentmods.dev/badge/commands/nexenio/bifrost-plugin/bifrost-debug/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/commands/nexenio/bifrost-plugin/bifrost-debug"><img src="https://agentmods.dev/badge/commands/nexenio/bifrost-plugin/bifrost-debug.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00018 | $0.00102 |
| Opus 5.5 | $0.00007 | $0.00041 |
| Sonnet 5.5 | $0.00004 | $0.00020 |
| Haiku 4.5 | $0.00002 | $0.00010 |
Grade A, and why
bifrost-debug 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.
What it actually says
/bifrost-debug
Diagnose why the Bifrost gateway, memory injection, or skill discovery isn't working in Claude Code.
Load and follow the bifrost-debug skill (skills/bifrost-debug/SKILL.md)
decision tree. Natural-language triggers such as "bifrost not working" or "mcp not
connecting" invoke the same skill.
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 · 13 lines · 18 tokens per session scan A fc60ca2196e1
bifrost-debug is a command published in the GitHub repository neXenio/bifrost-plugin (4 stars, last pushed 8d ago), licensed MIT. It adds 18 tokens to every session and 102 once invoked, about $0.0001 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-31.
Other commands, from other repositories
ccc-debug-session
Run a structured debug session: gather context, rank hypotheses, test them without editing code, then fix with a regression test and record the lesson. Use when a bug's cause is unclear.
scan
A codebase onboarding briefing that examines a new project's files, tools, main entry points, and marked technical debt.
perf
Structured performance investigation with baselines, profiling, and evidence-backed decisions.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
fix
Execute audit findings by ID (human-gated) -- re-verify, fix, prove, ledger.
parallax-status
Summarize the current session and run package/native lifecycle diagnostics.