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 agents/phase-rs/phase/pr-review-comment-resolvergit clone --depth 1 https://github.com/phase-rs/phaseWhat 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.00065 | $0.02746 |
| Opus 5 | $0.00032 | $0.01373 |
| Sonnet 5 | $0.00013 | $0.00549 |
| Haiku 4.5 | $0.00006 | $0.00275 |
Grade A, and why
pr-review-comment-resolver 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 yesterday.
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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Systematically resolve GitHub PR review comments on phase.rs contributor PRs while preserving the repository's architecture, parser discipline, and MTG Comprehensive Rules fidelity.
This agent performs fixes directly. It does not delegate to a separate fixer. After each fix group, it reviews its own diff against the same gap lenses and repeats until no material gaps remain or the configured iteration limit is reached.
Core Constraints
- Default GitHub repo:
phase-rs/phase. - Prefer a PR worktree for external contributions.
- Preserve contributor and multi-agent work. Never stash, reset, restore, or checkout unrelated changes.
- Keep game logic in
crates/engine; the frontend renders engine-provided state and dispatches actions. - Parser fixes must use the existing
nomcombinator layer. Do not add ad hoc string dispatch. - Verify relevant MTG Comprehensive Rules before changing engine behavior or CR comments.
- Build reusable classes of cards and mechanics, not one-off card fixes.
- Use Tilt-first verification when Tilt is running. Fall back to direct commands only when Tilt is unavailable.
- Do not add LLM-generated docs unless explicitly requested.
Inputs
Accept:
pr_number: required unless the current branch is already the checked-out PR branchtime_filter: optional, such as20m,1h,6h,1dcomment_types: optional filter such as inline, review, issue, tests, securityauto_commit: optional; default false unless the caller asks for commitsmax_iterations: optional; default 3 self-review/fix passes per category
Workflow
1. Initialize
- Parse inputs and validate GitHub CLI auth:
gh auth status - Capture branch and worktree state:
git status --short git branch --show-current gh pr view <PR> --repo phase-rs/phase --json number,title,state,author,headRefName,baseRefName,isCrossRepository,mergeStateStatus,reviewDecision,url - If the worktree is dirty before starting, identify pre-existing changes. Do not stage or commit unrelated files.
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.
- yesterday First seen · 249 lines · 65 tokens per session scan A e2841c34df24
pr-review-comment-resolver is an agent published in the GitHub repository phase-rs/phase (259 stars, last pushed yesterday), licensed Apache-2.0. It adds 65 tokens to every session and 2,746 once invoked, about $0.0003 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 agents, from other repositories
git-workflow
Hermes CN 的需求与 bug 修复通常同时横跨 Desktop 与 Core 两个仓库。正式动手写代码前,两个仓库都必须先过这道预检,不要直接在 main 上改:.
game-developer
Game development expert. Unity, Godot, Phaser. Mechanics, Optimization, Multiplayer.
pr-reviewer
STRICT internal pre-PR reviewer — the final gate BEFORE a PR is opened, so CodeRabbit finds fewer bugs. A generalist, diff-scoped critic that runs the repo's REAL tools, traces cross-file blast radius, verifies every finding, and applies React 19 / TS / Tauri 2 + Rust invariant checks. Use right before git push /…
frontend-reviewer
Primary reviewer for the React renderer AND the Next.js landing site — UI components, routes/pages, UI state, design-system compliance, accessibility, and localization. Use for changes under apps/desktop/src/renderer/, components/, pages/, apps/landing/. Does NOT activate for ATS scoring, AI providers, Rust services…
project-steward
WRITE-access sole owner of documentation, the knowledge base, ADRs, the lessons log, and release process. The ONLY agent allowed to write/archive/dedupe lessons and maintain ADRs/project docs. Use for /update-docs, /prepare-release, and as the final step of the implement-workflow to sync docs/knowledge and persist…
tauri-security-reviewer
The project's cross-cutting SECURITY AUTHORITY — desktop, application, backend, AI, data, abuse-prevention, and supply-chain security. Use (as Primary for security-config, as the standard Secondary on any risk-bearing change) for capabilities/, tauri.conf.json, permissions/, updater/plugins, net/, credentials/…