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 chiruu12/OSS-Skills --skill oss-review-prsgit clone --depth 1 https://github.com/chiruu12/OSS-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/chiruu12/oss-skills/oss-review-prs)<a href="https://agentmods.dev/skills/chiruu12/oss-skills/oss-review-prs"><img src="https://agentmods.dev/badge/skills/chiruu12/oss-skills/oss-review-prs/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/chiruu12/oss-skills/oss-review-prs"><img src="https://agentmods.dev/badge/skills/chiruu12/oss-skills/oss-review-prs.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.00092 | $0.02472 |
| Opus 5 | $0.00046 | $0.01236 |
| Sonnet 5 | $0.00018 | $0.00494 |
| Haiku 4.5 | $0.00009 | $0.00247 |
Grade A, and why
oss-review-prs 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 12d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review PRs
Review other people's PRs to learn how the codebase evolves and earn maintainer trust. Thoughtful reviews are the fastest way from outsider to recognized contributor — maintainers notice reviewers who catch real issues.
Purpose
Most contributors jump straight to writing code. But reviewing PRs teaches you things that reading source code doesn't: what maintainers care about, what patterns are enforced vs. aspirational, how the code changes over time, and what mistakes other contributors make. Regular reviewers build relationships with maintainers and earn trust that makes their own PRs get reviewed faster.
When to Use
- You want to learn a codebase before contributing code
- You want to build trust with maintainers as a new contributor
- You've merged one PR and want to become a regular (see
oss-second-contribution) - You want to practice code review skills on real codebases
- NOT for reviewing your own PR before submission — use
oss-submit-prfor self-review - NOT if you don't understand the codebase at all — use
oss-explore-repofirst
Prerequisites
- Repo explored enough to understand the general architecture (from
oss-explore-repooross-prep-to-contribute) ghCLI authenticated- Understanding of the language and frameworks used (or willingness to learn via
oss-learn-stack)
Process
1. Find PRs worth reviewing
Not every open PR needs your review. Pick ones where your review adds value.
# Open PRs, sorted by most recent
gh pr list -R {owner}/{repo} --state open --json number,title,author,labels,reviewDecision,createdAt,additions,deletions \
--jq '.[] | "\(.number)\t\(.additions)+\(.deletions)\t\(.author.login)\t\(.title)"'
# PRs from first-time contributors (maintainers appreciate help reviewing these)
gh api "repos/{owner}/{repo}/pulls?state=open&per_page=30" \
--jq '.[] | select(.author_association == "FIRST_TIME_CONTRIBUTOR" or .author_association == "NONE")
| "#\(.number)\t\(.user.login)\t\(.title)"'
# PRs without any reviews yet
gh pr list -R {owner}/{repo} --state open --json number,title,reviews \
--jq '.[] | select(.reviews | length == 0) | "\(.number)\t\(.title)"'
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.
- 12d ago First seen · 222 lines · 92 tokens per session scan A a45a3e045634
oss-review-prs is a skill published in the GitHub repository chiruu12/OSS-Skills (63 stars, last pushed 18d ago), licensed MIT. It adds 92 tokens to every session and 2,472 once invoked, about $0.0005 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
solid-principles
SOLID principles checklist with Java examples. Use when a class has too many responsibilities, an abstraction leaks, or a dependency points the wrong way, and when the user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation or Dependency Inversion. For naming, duplication and method length…
architecture-review
Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering. Use when user asks "review architecture", "check structure", "package organization", or when evaluating if a codebase follows clean architecture principles.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
clean-abap
Clean ABAP coding standards and best practices. Use when writing ABAP code, reviewing ABAP code, or refactoring ABAP code to ensure it follows SAP's official Clean ABAP style guide. Covers naming conventions, modern language constructs, class/method design, error handling, formatting, comments, and unit testing…
review-r
Read-only R code review protocol for .R scripts. Checks code quality, reproducibility, domain correctness, tidyverse idioms, and professional standards; produces a report without editing. Use when user says "review this R script", "check the R code", "audit the analysis code", "code review on the R", or when an R file…