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/stilero/claude-pluginsWrote 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/stilero/claude-plugins/fix-pr-comments-loop)<a href="https://agentmods.dev/commands/stilero/claude-plugins/fix-pr-comments-loop"><img src="https://agentmods.dev/badge/commands/stilero/claude-plugins/fix-pr-comments-loop/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/stilero/claude-plugins/fix-pr-comments-loop"><img src="https://agentmods.dev/badge/commands/stilero/claude-plugins/fix-pr-comments-loop.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.00033 | $0.00296 |
| Opus 5.5 | $0.00013 | $0.00118 |
| Sonnet 5.5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
fix-pr-comments-loop 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 Loop
FIRST: Load the fix-pr-comments-loop skill using the Skill tool to understand what you are expected to do and follow the instructions exactly.
This command is a thin wrapper around the fix-pr-comments-loop skill. The skill orchestrates pr-comment-fixer:fix-issues and hardcore-code-reviewer:hardcore-code-reviewer into a single autonomous outer loop that drives a PR to a clean review state.
If $ARGUMENTS is provided:
- User has given a specific Pull Request number:
$ARGUMENTS - Use this Pull Request number when running the
fix-pr-comments-loopskill instead of inferring it from the current branch.
If $ARGUMENTS is empty:
- Infer the PR from the current branch as documented in the
fix-pr-comments-loopskill. - If no open PR exists for the current branch, fail fast with a clear message (per the skill's no-open-PR contract).
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 · 21 lines · 33 tokens per session scan A 1c1f12b3cbf6
fix-pr-comments-loop is a command published in the GitHub repository stilero/claude-plugins (2 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 296 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
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
factory
Linha de montagem multi-agente (Software Factory) — spec-writer → builder em worktree isolado → 4 revisores paralelos (Security, Code, UI, UX) → approver com gate de risco e dashboard visual.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
release-tag
Create and push a version tag after a release PR has been merged.