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 skills add mostafa-drz/claude-skills --skill address-pr-feedbackgit clone --depth 1 https://github.com/mostafa-drz/claude-skillsWrote 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/mostafa-drz/claude-skills/address-pr-feedback)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/address-pr-feedback"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/address-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/mostafa-drz/claude-skills/address-pr-feedback"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/address-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.00061 | $0.01936 |
| Opus 5.5 | $0.00024 | $0.00774 |
| Sonnet 5.5 | $0.00012 | $0.00387 |
| Haiku 4.5 | $0.00006 | $0.00194 |
Grade A, and why
address-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 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.
How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Address PR Feedback
Comprehensive PR review workflow that fetches all comments, uses parallel agents for critical analysis, makes implementation decisions, then systematically addresses valid concerns with incremental commits and browser validation.
Preferences
On startup, use Read to load ~/.claude/skills/address-pr-feedback/preferences.md. If file doesn't exist, use defaults.
Context
On startup, use Bash to detect: current git branch, git status, repo name, and check for localhost development server. Skip any that fail.
Command routing
Check $ARGUMENTS:
help→ display help then stopconfig→ interactive setup then stopreset→ delete preferences file, confirm, stop- PR number/URL with optional flags → run the workflow
Help
Address PR Feedback — Systematic PR review implementation with agent validation
Usage:
/address-pr-feedback <pr-number|url> Process all PR feedback
/address-pr-feedback #123 --dry-run Analyze only, no changes
/address-pr-feedback #123 --auto-push Skip push confirmation
/address-pr-feedback #123 --no-browser Skip browser validation
/address-pr-feedback config Set preferences
/address-pr-feedback reset Clear preferences
/address-pr-feedback help This help
Examples:
/address-pr-feedback #123 Full workflow for PR 123
/address-pr-feedback https://github.com/owner/repo/pull/456
/address-pr-feedback #789 --dry-run --no-browser
Current preferences:
localhost-port: 3000 (or "auto-detect")
browser-validation: enabled (or "disabled")
auto-commit: true (or "false")
agent-analysis: parallel (or "sequential")
Config
Use AskUserQuestion to collect:
- Q1: Default localhost port — 3000, 3001, 4000, auto-detect
- Q2: Browser validation — Always validate, Skip for non-UI changes, Always skip
- Q3: Commit behavior — Auto-commit after each fix, Ask before each commit
- Q4: Agent analysis — Parallel (faster), Sequential (more thorough)
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 Changed · +3 lines 61d42138158d
- 1mo ago First seen · 205 lines · 61 tokens per session scan A e48f8407fb9e
address-pr-feedback is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 1,936 once invoked, about $0.0002 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
visual-explainer-diff
Use when asked to visualize, explain, or document what changed between two git refs in a codebase. Triggers: 'show what changed in this PR', 'visualize the diff', 'explain the changes between main and this branch', 'generate a change report', 'what did this commit change architecturally', or any request to understand…
understand-diff
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks.
skills-pr-handle
Use when explicitly asked to handle a pull request in the Scenario skills repository, including review comments and skill validation.
pr-handle-comments
Handle review comments received on GitHub for the current branch's PR or a given PR number or URL, by triaging each unresolved thread, fixing what is warranted, pushing, and replying in each thread, when asked to address, fix or answer PR comments. Works in any Scenario repository.
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
work-with-pr
Full PR lifecycle in a fresh task-owned git worktree: implement via the ulw-loop skill with mandatory evidence-bound manual QA → reviewer-readable English PR → verification loop (CI + Cubic, where Cubic is skipped only when its quota is exhausted) → merge by default → worktree cleanup. Decomposes one task into the…