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 commands/fusengine/agents/fix-pr-commentsgit clone --depth 1 https://github.com/fusengine/agentsWhat 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.00018 | $0.00397 |
| Opus 5 | $0.00009 | $0.00198 |
| Sonnet 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 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.
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.
- yesterday First seen · 64 lines · 18 tokens per session scan A 19e48ebd1cef
fix-pr-comments is a command published in the GitHub repository fusengine/agents (25 stars, last pushed 28d ago), licensed MIT. It adds 18 tokens to every session and 397 once invoked, about $0.0001 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 commands, from other repositories
burn-rate
Compute the recent 7-day spend trend (burn rate) from daily sessions and per-session cost.
profile
Coordinate a reproducible Java profiling and optimization lifecycle.
update-issue
Update an issue description with structured, evidence-backed content.
publish-skill
Sync a marketplace skill to the documentation site. Creates skill detail pages (EN/ZH), updates the marketplace index, and updates docs.json navigation.
deploy
Deploy Solana program (devnet first, then mainnet).
generate-idl-client
Generate TypeScript client from Solana program IDL using Codama or Anchor.