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 skills/zate/cc-plugins/pr-feedbacknpx skills add Zate/cc-plugins --skill pr-feedbackgit clone --depth 1 https://github.com/Zate/cc-pluginsWhat 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.00026 | $0.01124 |
| Opus 5 | $0.00013 | $0.00562 |
| Sonnet 5 | $0.00005 | $0.00225 |
| Haiku 4.5 | $0.00003 | $0.00112 |
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 2d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Feedback - Integrate Review Comments
Fetch PR review feedback and add actionable items to the plan. You do the work directly.
Step 1: Identify PR
If PR number provided: Use $ARGUMENTS
Otherwise, detect from current branch:
gh pr view --json number,title,state,reviewDecision
If no PR found for current branch, inform user and exit.
Step 2: Fetch Feedback
Get PR details:
gh pr view --json number,title,body,reviews,reviewDecision,comments
Get inline code comments:
gh api repos/{owner}/{repo}/pulls/{number}/comments --jq '.[] | {path, line, body, user: .user.login}'
Step 3: Parse Comments
Categorize each comment:
| Pattern | Category |
|---|---|
| Review state = CHANGES_REQUESTED | Blocker |
| "must", "need to", "please fix" | Blocker |
| "should", "consider", "might" | Suggestion |
| "why", "what if", "?$" | Question |
| "nit", "minor", "optional" | Nitpick |
Extract actionable items:
For each comment/review body:
- Check if it requests action
- Summarize the request
- Note the author
- Track file/line if inline comment
Step 4: Present Findings
Display to user:
## PR #123 Feedback
**Status**: CHANGES_REQUESTED by @reviewer
### Blockers (must address)
1. Fix null handling in parseConfig (src/config.ts:42)
2. Add tests for edge cases
### Suggestions
3. Consider caching the parsed config
### Questions (respond or address)
4. Why not use the existing parser?
### Nitpicks (optional)
5. Rename variable for clarity
Ask which to add to plan:
AskUserQuestion:
questions:
- question: "Which feedback items should be added to the plan?"
header: "Select"
multiSelect: true
options:
- label: "All blockers"
description: "Add items 1-2"
- label: "Blockers + suggestions"
description: "Add items 1-3"
- label: "All items"
description: "Add everything"
- label: "Select individually"
description: "Choose specific items"
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.
- 2d ago First seen · 209 lines · 26 tokens per session scan A 1fbfd255ae49
pr-feedback is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 1,124 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.