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/thrownlemon/claude-code-plugins/cr-prnpx skills add ThrownLemon/claude-code-plugins --skill cr-prgit clone --depth 1 https://github.com/ThrownLemon/claude-code-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.00023 | $0.00494 |
| Opus 5 | $0.00012 | $0.00247 |
| Sonnet 5 | $0.00005 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
cr-pr 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.
What it actually says
PR Review Comment Management
When the user wants to view or address review comments on a pull request, delegate to the cr-pr-manager subagent.
When to Use
Use this skill when the user:
- Asks about PR comments or review feedback
- Wants to see unresolved review comments
- Mentions CodeRabbit comments on a PR
- Wants to address or resolve review feedback
- Asks about comments from reviewers (bots or humans)
What the Subagent Handles
The cr-pr-manager subagent will:
-
Identify PR
- Auto-detect from current branch
- Or use specified PR number
-
Fetch ALL Comments
- CodeRabbit comments via MCP
- GitHub review comments (other bots)
- GitHub reviews (human reviewers)
-
Categorize by Reviewer
- CodeRabbit (AI review bot)
- Other bots (SonarCloud, Codacy, Snyk, etc.)
- Human reviewers (team members)
-
Present Comments
- Group by reviewer, then by severity/file
- Show resolution status
- Include file paths and line numbers
-
Interactive Actions
- View full comment details
- Apply suggested fixes
- Mark as resolved
- Reply to comments
- Filter by reviewer/file/severity
Comment Sources
This skill aggregates feedback from multiple sources:
- CodeRabbit MCP: AI review comments with fix suggestions
- GitHub API: Human reviewer comments and other bot feedback
Example Triggers
- "Show me the PR review comments"
- "What are the unresolved comments on my PR?"
- "Help me address the CodeRabbit feedback"
- "Are there any review comments I need to fix?"
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 · 75 lines · 23 tokens per session scan A 78faeca075fe
cr-pr is a skill published in the GitHub repository ThrownLemon/claude-code-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 494 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…