Claude Code Skills Marketplace is a collection and marketplace of skills, plugins, agents, and instructions that extend Claude Code with specialized development workflows. It is for developers who want to install existing workflows or create, validate, and package their own Claude Code skills.
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 daymade/claude-code-skills --skill github-review-prgit clone --depth 1 https://github.com/daymade/claude-code-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/daymade/claude-code-skills/github-review-pr)<a href="https://agentmods.dev/skills/daymade/claude-code-skills/github-review-pr"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/github-review-pr/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/daymade/claude-code-skills/github-review-pr"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/github-review-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00086 | $0.06557 |
| Opus 5.5 | $0.00034 | $0.02623 |
| Sonnet 5.5 | $0.00017 | $0.01311 |
| Haiku 4.5 | $0.00009 | $0.00656 |
Grade A, and why
github-review-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 3d 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 — 562 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review a Contributor PR as Maintainer
Treat every verdict as a claim about exact immutable Git objects. Review each PR's prospective effect on the current base branch, not a stale web diff or an old review snapshot. A queue review is a sequence of independent PR reviews, never one shared approval or mutation batch.
Default to read-only. Do not comment, approve, request changes, update the branch, push, close, merge, enable auto-merge, bypass protections, or delete a branch unless the user explicitly authorizes that exact external mutation.
Use $ARGUMENTS as the target. Strip the recognized --personal-maintainer and
--all-open flags before parsing it. If neither a PR nor an explicit all-open request
can be resolved after inspecting the current repository and conversation, ask for the
PR URL, owner/repo#number, or confirmation that all open PRs are in scope.
Route the Request
Use this workflow for any of these:
- One open GitHub PR when the outcome is review, re-review, merge-readiness, review-led repair, or review-led landing.
- One explicitly named closed-unmerged PR when the user wants a retrospective merit review, wants to know why it closed, or is considering whether it should stay closed or be reopened. Reopening remains a separate mutation.
- All currently open contributor PRs in one repository when the user explicitly asks
for an open-PR queue review. Process them by
createdAtfrom newest to oldest and issue one evidence ledger and decision per PR. - An author's own contribution only when the user explicitly requests an independent
maintainer-style evaluation. Apply the same immutable-object and counter-review
method in read-only mode; do not switch to personal-maintainer mode, post a formal
approval, or acquire merge authority. Return the verdict to the author; authorized
repairs remain with
github-contributor:github-contributor.
Use a narrower workflow instead when the request is only one of these:
- Create or administer PRs, issues, repositories, or workflows.
- Diagnose CI without reviewing the code change.
- Address already-filed review comments without performing a fresh review.
- Merge an already-reviewed PR without performing a fresh review.
- Review an unpushed local branch or working-tree diff.
- Run a security-only diff audit.
- Sweep issues, all closed PRs as review targets, documents, settings, or unrelated repository state. A single explicitly named closed PR is allowed above; historical closed-PR comments may also be read as maintainer precedent in personal mode.
What ships with it
4 files 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.
- 3d ago Changed · +17 lines 43c679fd1028
- 7d ago Changed · +10 lines 9286b4b8ef29
- 8d ago Changed · +22 lines · -15 tokens per session e5d731657495
- 24d ago Changed · +4 lines · -86 tokens per session 65bed00c8b52
- 29d ago Changed · +21 lines 5b4f2edad76e
- 1mo ago First seen · 488 lines · 187 tokens per session scan A cfa766acfc0c
github-review-pr is a skill published in the GitHub repository daymade/claude-code-skills (1,473 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 6,557 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
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.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…