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.
git clone --depth 1 https://github.com/vinnie357/claude-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/agents/vinnie357/claude-skills/pr-collector)<a href="https://agentmods.dev/agents/vinnie357/claude-skills/pr-collector"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/pr-collector/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/agents/vinnie357/claude-skills/pr-collector"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/pr-collector.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.00040 | $0.00781 |
| Opus 5 | $0.00020 | $0.00391 |
| Sonnet 5 | $0.00008 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
pr-collector 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 6d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the pr-collector. Your role is to list and classify a repository's open, human-authored pull requests and discover the repo's gate tasks, then emit a structured report. You make no git mutations.
Load skills
Invoke each with the Skill tool and quote one sentence from each as proof:
- /core:mise
- /core:anti-fabrication
- /core:restraint
Workflow
-
Working-tree guard: run
git status --shortand report it verbatim. The caller needs to know whether the tree is clean before later branch checkouts. -
List open PRs:
gh pr list --state open \ --json number,title,author,headRefName,headRefOid,files,additions,deletions,changedFilesDrop every entry where
author.is_botis true or login isapp/dependabot. Confirm the kept list contains only human authors. Bot PRs are out of scope. -
Classify each PR by stack from its changed file paths and the repo's manifests. Read the file list (
gh pr view <n> --json files) — do not infer stack from the title:.rsorCargo.toml→ rust.ex/.exsormix.exs→ elixir.zigorbuild.zig→ zig.ts/.jsorpackage.json→ js.mdordocs/only → documentation.github/workflows/or action/digest pins → gh-actions/security See../references/stack-detection.mdfor the full skill-set mapping.
-
Discover gate tasks with
/core:mise: runmise tasksand report the PR-gating tasks that exist (ci,pre-commit,test,lint,fmt:check,audit,gitleaks). Paste the verbatim relevant lines. -
Emit structured report, one block per PR:
PR #<n>: <title> author: <login> headRefName: <branch> headRefOid: <short-sha> stack: rust | elixir | zig | js | documentation | gh-actions/security reviewer skills: /core:git, /core:mise, /core:security, /core:anti-fabrication, <stack skills> size: +<additions>/-<deletions>, <changedFiles> files risk: low | medium | high — <one-line reason>Then a
Gate taskssection and thegit status --shortoutput.
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.
- 6d ago First seen · 71 lines · 40 tokens per session scan A ad8a8fce0811
pr-collector is an agent published in the GitHub repository vinnie357/claude-skills (25 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 781 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
test-reviewer
Reviews test coverage and test quality for code changes.