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-post-prgit 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-post-pr)<a href="https://agentmods.dev/skills/chiruu12/oss-skills/oss-post-pr"><img src="https://agentmods.dev/badge/skills/chiruu12/oss-skills/oss-post-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/chiruu12/oss-skills/oss-post-pr"><img src="https://agentmods.dev/badge/skills/chiruu12/oss-skills/oss-post-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.00090 | $0.02451 |
| Opus 5 | $0.00045 | $0.01226 |
| Sonnet 5 | $0.00018 | $0.00490 |
| Haiku 4.5 | $0.00009 | $0.00245 |
Grade A, and why
oss-post-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 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-PR Review
Your PR got reviewed. Now what? This skill helps you understand what reviewers are actually asking for, why they're asking for it, and how to address their feedback - without writing the code for you.
Purpose
Review comments from maintainers are often terse. "Can you use X pattern instead?" doesn't explain WHY X is preferred, or WHERE to find examples of it. This skill bridges that gap: it researches the reviewer's concern, finds examples in the codebase, and explains the reasoning - so you can address feedback intelligently instead of blindly copy-pasting.
Prerequisites
- A submitted PR with review comments (from
oss-submit-pr) - The repo cloned locally with your working branch checked out
Process
1. Fetch all review feedback
# Get PR reviews
gh pr view {pr-number} -R {owner}/{repo} --json reviews,comments,reviewDecision,statusCheckRollup
# Get review comments (inline code comments)
gh api repos/{owner}/{repo}/pulls/{pr-number}/comments --jq '.[] | {path: .path, line: .line, body: .body, user: .user.login, state: .state}'
# Get PR conversation comments
gh api repos/{owner}/{repo}/issues/{pr-number}/comments --jq '.[] | {body: .body, user: .user.login, createdAt: .created_at}'
2. Categorize feedback
Sort each piece of feedback into categories:
| Category | What it means | How to handle |
|---|---|---|
| Blocking | "This must change before merge" | Address immediately |
| Suggestion | "Consider doing X" / "nit:" | Evaluate - adopt if it improves the code |
| Question | "Why did you do X?" | Explain your reasoning (this tests YOUR understanding) |
| Style | "We prefer X convention" | Follow it - this is the repo's house rules |
| Scope | "This should be a separate PR" | Split if reviewer insists |
Present the categorized list:
## PR Review Summary: #{pr-number}
**Overall decision**: {approved / changes requested / commented}
### Blocking
1. `src/foo.ts:42` - {reviewer}: "{comment}" → **Must fix**
2. ...
### Suggestions
1. `src/bar.ts:15` - {reviewer}: "{comment}" → **Evaluate**
2. ...
### Questions (you need to answer these)
1. {reviewer}: "{question}" → **Explain your reasoning**
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 · 229 lines · 90 tokens per session scan A 50885390eebc
oss-post-pr is a skill published in the GitHub repository chiruu12/OSS-Skills (62 stars, last pushed 17d ago), licensed MIT. It adds 90 tokens to every session and 2,451 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
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
ln-63-release-publisher
Prepares and publishes an explicitly requested tagged GitHub release. Not for ordinary commits, package publication, or announcements.
ln-64-community-announcer
Drafts or publishes fact-checked GitHub Discussions announcements for project updates. Not for release creation or issue responses.
conventions-check
Review a pull request's title, description, and scope against the repository's PR conventions.
056-design-avoid-breaking-changes
Use when you need to review a plan, OpenSpec change, specification, or implementation proposal for breaking-change risk across commands, skills, generated outputs, XML sources, README/docs, tests, CI, APIs, schemas, configuration, data, migration, and release guidance. This should trigger for requests such as Review…