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/fusengine/agentsWrote 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/fusengine/agents/fix-pr-comments)<a href="https://agentmods.dev/commands/fusengine/agents/fix-pr-comments"><img src="https://agentmods.dev/badge/commands/fusengine/agents/fix-pr-comments/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/fusengine/agents/fix-pr-comments"><img src="https://agentmods.dev/badge/commands/fusengine/agents/fix-pr-comments.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.00397 |
| Opus 5.5 | $0.00007 | $0.00159 |
| Sonnet 5.5 | $0.00004 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
fix-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 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
Fix PR Comments
Systematically address all PR review comments:
-
Fetch PR Comments:
gh pr view [PR_NUMBER] --comments gh api repos/{owner}/{repo}/pulls/[PR_NUMBER]/comments -
Categorize Comments:
- Must Fix: Blocking issues (security, bugs, breaking changes)
- Should Fix: Code quality, performance, best practices
- Nice to Have: Style preferences, minor suggestions
- Questions: Clarifications needed
-
Address Each Comment: For each comment:
- Locate relevant file and line
- Understand the requested change
-
Use research-expert if clarification needed on best practices
- Apply fix following project patterns
- Mark comment as resolved
-
Run Quality Checks:
Use sniper to ensure all changes maintain code quality
bun run lint bun test -
Commit Fixes:
git commit -m "$(cat <<'EOF' fix: Address PR review comments - [Comment 1 fix] - [Comment 2 fix] - [Comment 3 fix] EOF )" -
Push and Notify:
git push gh pr comment [PR_NUMBER] --body "✅ All review comments addressed"
Arguments:
- $ARGUMENTS specifies PR number or focuses on specific comment type
Example Usage:
/fix-pr-comments 123→ Fix all comments for PR #123/fix-pr-comments→ Fix comments for current PR
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 · 64 lines · 18 tokens per session scan A 19e48ebd1cef
fix-pr-comments is a command published in the GitHub repository fusengine/agents (31 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 397 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-30.
Other commands, from other repositories
improve
Start the autonomous improvement loop using isolated git worktrees.
fix-pr
Fetch and resolve unresolved PR comments.
review-changes
Review uncommitted changes and suggest improvements.
odoo-review
Review a GitHub PR against Odoo PSDU conventions — business need, file-by-file, then full-logic; before/after fixes; terminal-only, read-only.
nyann:sync
Update the current feature branch against its base (rebase by default, merge on request). Refuses on main/master/develop or with a dirty tree.
review
Run a Gemini code review against local git state.