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 glincker/claude-code-marketplace --skill pr-reviewergit clone --depth 1 https://github.com/glincker/claude-code-marketplaceWrote 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/glincker/claude-code-marketplace/pr-reviewer)<a href="https://agentmods.dev/skills/glincker/claude-code-marketplace/pr-reviewer"><img src="https://agentmods.dev/badge/skills/glincker/claude-code-marketplace/pr-reviewer/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/glincker/claude-code-marketplace/pr-reviewer"><img src="https://agentmods.dev/badge/skills/glincker/claude-code-marketplace/pr-reviewer.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.00018 | $0.02401 |
| Opus 5 | $0.00009 | $0.01201 |
| Sonnet 5 | $0.00004 | $0.00480 |
| Haiku 4.5 | $0.00002 | $0.00240 |
Grade A, and why
pr-reviewer 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 10d 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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous PR Reviewer
⚡ UNIQUE FEATURE: Multi-agent review system with specialized reviewers for security, performance, testing, and architecture - the first autonomous PR review skill with parallel agent coordination.
What This Skill Does
Automatically reviews pull requests with multiple specialized AI agents working in parallel:
- Security Agent: Scans for vulnerabilities, SQL injection, XSS, hardcoded secrets
- Performance Agent: Identifies bottlenecks, inefficient algorithms, memory leaks
- Testing Agent: Validates test coverage, suggests additional test cases
- Architecture Agent: Reviews design patterns, code structure, maintainability
- Style Agent: Checks code style, naming conventions, documentation
Why This Is Unique
Unlike simple code review tools, this skill:
- Runs 5 specialized agents in parallel for comprehensive analysis
- Provides actionable suggestions with code examples
- Generates review summaries for different audiences (technical/non-technical)
- Auto-suggests fixes that you can apply with one command
- Learns from your codebase patterns and conventions
Instructions
Phase 1: Setup and Discovery
-
Identify the PR:
- Use Bash to get current branch and diff:
git diff main...HEAD - Or accept PR number/URL from user
- Use Bash:
gh pr view <number>to get PR details
- Use Bash to get current branch and diff:
-
Gather Context:
- Use Glob to find all changed files
- Use Read to examine modified code
- Use Grep to search for related code patterns
- Identify programming languages and frameworks
Phase 2: Multi-Agent Review (Parallel Execution)
Launch 5 specialized Task agents in parallel:
Agent 1: Security Reviewer
Task: Security analysis of PR
Prompt: "Analyze these code changes for security vulnerabilities:
- SQL injection risks
- XSS vulnerabilities
- Hardcoded secrets or API keys
- Authentication/authorization issues
- Dependency vulnerabilities
- OWASP Top 10 issues
Files: [list changed files]
Provide:
1. Severity ratings (Critical/High/Medium/Low)
2. Specific line numbers
3. Exploitation scenarios
4. Remediation steps with code examples"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 372 lines · 18 tokens per session scan A 0c1a19b437d9
pr-reviewer is a skill published in the GitHub repository glincker/claude-code-marketplace (36 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 2,401 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-30.
Other skills, from other repositories
audit
Use when the user wants a code review on recent changes — quality, spec, security, or performance feedback. Triggers a multi-level (L1-L5) review with a standalone Reviewer; on NEEDSFIX, offers to apply findings via /hyperflow:plan. Trigger with /hyperflow:audit, "review this change", "review my PR", "audit the diff"…
trace
Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find the root cause", "why…
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
pr
Use when reviewing an incoming GitHub pull request — runs the multi-level (L1-L5) audit against the PR's real diff range, posts findings as one batched review (inline, summary, or local-only), offers the standard fix chain on NEEDSFIX, and optionally merges. The maintainer-side counterpart to /hyperflow:issue. Trigger…
loop-converge
Author and optionally direct-launch a two-node loop-graph run whose North Star is code convergence — delete unused code, merge duplicates, reuse, slim. Use when the user invokes /loop-converge, or asks to loop on dead code, duplication, unused exports, DRY cleanup, or merging twin implementations. Starts the owner…
deep-security-audit
Multi-agent deep security audit — 6 expert personas (pentester, architect, code auditor, supply chain, data privacy, forensics) + CISO synthesis + optional fix implementation.