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/resolve-pr-commentsnpx skills add maximhq/bifrost --skill resolve-pr-commentsgit 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/resolve-pr-comments)<a href="https://agentmods.dev/skills/maximhq/bifrost/resolve-pr-comments"><img src="https://agentmods.dev/badge/skills/maximhq/bifrost/resolve-pr-comments.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.1 | $0.00000 | $0.02918 |
| Opus 5 | $0.00000 | $0.01459 |
| Sonnet 5 | $0.00000 | $0.00584 |
| Haiku 4.5 | $0.00000 | $0.00292 |
Grade A, and why
resolve-pr-comments 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 6d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: resolve-pr-comments description: Resolve all unresolved PR comments interactively. Makes local edits only—NEVER commits or pushes. Use when asked to resolve PR comments, address review feedback, handle CodeRabbit comments, or fix PR review issues. Invoked with /resolve-pr-comments <PR_NUMBER> or /resolve-pr-comments <owner/repo> <PR_NUMBER>. allowed-tools: Read, Grep, Glob, Bash, Edit, Write, WebFetch, Task, AskUserQuestion, TodoWrite
Resolve PR Comments
An interactive workflow to systematically address all unresolved PR review comments.
Usage
/resolve-pr-comments <PR_NUMBER>
/resolve-pr-comments <owner/repo> <PR_NUMBER>
If no repo is specified, uses the current git repository's remote origin.
Before starting the workflow - if the flow is in Plan Model - ask if the user wants to move to default mode to solve the comments one by one. Mention that each PR resolve has planning attached to it.
Workflow Overview
- Detect repository - Get owner/repo from git remote or user input
- Fetch unresolved comments - Use GitHub GraphQL API (REST doesn't expose resolved status). Paginate through
reviewThreads(cursor-based) so all pages are checked when a PR has more than 100 threads. - Create tracking file - Maintain state across the session
- For each comment:
- Get full details and any existing replies
- Show the diff view of existing code in a proper diff view
- Before suggesting the fix - do the research via documentations. And present all that docs research and relevant links to the user with the fix. Use context 7. MAKE SURE YOU DO THIS ALWAYS
- Present to user with options (FIX, REPLY, SKIP)
- Wait for user decision
- Execute the action
- Update tracking
- Verify resolution - Check remaining unresolved count
- Repeat until done - Continue until all comments resolved
Step 1: Detect Repository
If repository not provided, detect from git remote:
git remote get-url origin | sed -E 's|.*github.com[:/]([^/]+/[^/.]+)(\.git)?|\1|'
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.
- 6d ago First seen · 306 lines · 0 tokens per session scan A 753fea0e7b03
resolve-pr-comments is a skill published in the GitHub repository maximhq/bifrost (7,821 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,918 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
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.
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.
validation
Use this skill whenever MCPMate work needs test, lint, build, Inspector, or release-slice verification. Trigger on implementation, review, bug fixes, PR preparation, regression checks, or any request to validate backend, frontend, desktop, or MCP behavior before reporting completion.