Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add fivol/claude-make-better/plugin install featureWrote 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/fivol/claude-make-better/pr-feedback)<a href="https://agentmods.dev/skills/fivol/claude-make-better/pr-feedback"><img src="https://agentmods.dev/badge/skills/fivol/claude-make-better/pr-feedback/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/skills/fivol/claude-make-better/pr-feedback"><img src="https://agentmods.dev/badge/skills/fivol/claude-make-better/pr-feedback.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.00105 | $0.01493 |
| Opus 5.5 | $0.00042 | $0.00597 |
| Sonnet 5.5 | $0.00021 | $0.00299 |
| Haiku 4.5 | $0.00011 | $0.00149 |
Grade A, and why
pr-feedback 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 2mo 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR feedback — the reviewer's comments are work items
A comment on the PR is a work item exactly like the user's chat prompt. This skill owns both halves: collect before you implement, answer after you push. It never decides what the code should do — it makes sure no item is lost.
Two modes — say which one you are in
Invoked as /feature:pr-feedback collect or /feature:pr-feedback answer; with
no argument, collect. The modes are separated because they belong to opposite
ends of a pass, and running the wrong one is a real failure: answer before the
push cites no commit, and a second collect after the work re-opens items you
just handled.
| Mode | When | What it does |
|---|---|---|
collect |
before any code is written — workspace Phase 2, or ship step 0 standalone |
list unaddressed items, decide per item, hand the list back |
answer |
after the push — ship step 4b |
one reply per item picked up, each citing the fixing commit |
All plumbing is one script; never hand-roll it with gh api:
SC="${CLAUDE_PLUGIN_ROOT}/scripts/pr_feedback.py"
Behaviour is driven by the pr_feedback block of the config (enabled, reply,
resolve, include_outdated, include_bots, marker); with no config at all
the shipped defaults apply, so this works outside a workspace too.
collect — before implementing
python3 "$SC" list --cwd "$WT" [--pr <url>]
--pr when you know it (a workspace's .feature.json records it); omit it and
the current branch's own PR is used. pr_feedback.enabled: false, no PR yet, or
nothing unaddressed ⇒ one line of output and stop here, silently. A
gh/network failure (exit 2) is one line in the report, never a blocker.
A thread is unaddressed when it is unresolved and its last comment isn't yours. Two traps the script already handles — don't reintroduce them by hand:
ghposts as the human's own account, so the author tells you nothing; the marker in your own replies is the only discriminator.isOutdateddoes not mean handled — a comment goes outdated the moment you push a fix touching that file, so outdated threads are usually the ones just worked on. The digest carries the diff hunk for exactly that reason.
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.
- 2mo ago First seen · 120 lines · 105 tokens per session scan A 6a10369a670a
pr-feedback is a skill published in the GitHub repository fivol/claude-make-better (5 stars, last pushed 2mo ago), licensed MIT. It adds 105 tokens to every session and 1,493 once invoked, about $0.0004 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 skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…