Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jscraik/Agent-Skillsnpx agentmods add skills/jscraik/agent-skills/pr-green-sweepWrote 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/jscraik/agent-skills/pr-green-sweep)<a href="https://agentmods.dev/skills/jscraik/agent-skills/pr-green-sweep"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/pr-green-sweep/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/jscraik/agent-skills/pr-green-sweep"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/pr-green-sweep.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.00057 | $0.03100 |
| Opus 5.5 | $0.00023 | $0.01240 |
| Sonnet 5.5 | $0.00011 | $0.00620 |
| Haiku 4.5 | $0.00006 | $0.00310 |
Grade A, and why
pr-green-sweep 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 1mo 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Green Sweep
Collect findings, confirm the cause, repair within each PR's scope, and verify the result. Use an evidence-backed action queue; a required external failure blocks its PR's merge while independent repairs continue.
When To Use
- The user asks to monitor, fix, or keep rotating through open PRs until green.
- Open PRs need GitHub plugin/gh truth, CodeRabbit review fixes, CircleCI log triage, Context7 docs checks, merge, or cleanup.
- The user wants merged PR branches and worktrees pruned after merge proof.
- The user asks to review green PRs, resolve threads, merge them, and reconcile local branches in one foreground closeout.
Modes
review-fixis the default for named PR review-thread or CI repairs. Finish authorized foreground work; reportheartbeat_status: not_requested. Monitoring, merge, and cleanup are not implied by a request to fix findings.green-closeoutapplies to requested foreground review, thread resolution, merge, and local reconciliation. Carry the named operations through their evidence gates without duplicate confirmation; reportheartbeat_status: not_requested. A request to reconcile branches authorizes inspection and safe updates, not blanket branch or worktree deletion.monitor-closeoutapplies when the user requests recurring continuation. Reuse or create one heartbeat with target PRs, notification intent, and a scope-specific stop rule. A blocked monitor blocks scheduled continuation only; it does not block already-authorized foreground repairs.- Merge and cleanup run only when explicitly included in the user's scope. Preserve standing authorization; do not ask again for unchanged authorized operations. Readiness gates and execution approvals still apply.
Read Review Findings for collection, confirmed issue triage, head changes, and the fix-to-resolution proof sequence. The mode rules here govern older closeout capsules and fixtures: heartbeat requirements apply to scheduled work, and cleanup requirements apply only to cleanup.
What ships with it
26 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.
- references/closeout-commander.md 17 KB
- references/contract.yaml 17 KB
- references/eval-scenarios.json 54 KB
- references/evals.yaml 85 KB
- references/evals/eval.harness.local-pass-ci-unknown.md 1.5 KB
- references/evals/eval.harness.pr-lifecycle-stops-before-main.md 1.7 KB
- references/evals/eval.pr-green-sweep.admin-merge-pressure.md 702 B
- references/evals/eval.pr-green-sweep.blocked-external-ci-keeps-independent-lanes-visible.md 1.2 KB
- references/evals/eval.pr-green-sweep.cleanup-without-merge-proof.md 1.6 KB
- references/evals/eval.pr-green-sweep.rotation-without-heartbeat.md 1.8 KB
- references/evals/eval.pr-green-sweep.stale-green-checks.md 1.6 KB
- references/evals/eval.pr-green-sweep.status-summary-without-queue.md 1.6 KB
- references/evals/eval.pr-green-sweep.wrong-validator-for-reference-doc.md 1.8 KB
- references/knowledge-capsule-routing.md 1.9 KB
- references/knowledge-capsule.manifest.yaml 9.0 KB
- references/knowledge-capsules/pr-green-sweep-action-queue.md 7.8 KB
- references/knowledge-capsules/pr-green-sweep-authorization-and-blockers.md 6.4 KB
- references/knowledge-capsules/pr-green-sweep-cleanup-proof.md 8.4 KB
- references/knowledge-capsules/pr-green-sweep-heartbeat-and-scope.md 8.8 KB
- references/knowledge-capsules/pr-green-sweep-live-pr-evidence.md 12 KB
- references/knowledge-capsules/pr-green-sweep-validation-surface.md 9.7 KB
- references/knowledge-demand.yaml 982 B
- references/recurring-finding-ledger.v1.schema.json 3.0 KB
- references/review-findings.md 6.0 KB
- references/task-profile.json 1.4 KB
- scripts/validate_recurring_findings.py 2.8 KB runs code
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.
- 1mo ago Changed · +8 lines · -2 tokens per session 957f05728283
- 1mo ago Changed · +38 lines · +8 tokens per session a30388d81f16
- 1mo ago First seen · 204 lines · 51 tokens per session scan A 2eb34dbb30b7
pr-green-sweep is a skill published in the GitHub repository jscraik/Agent-Skills (9 stars, last pushed yesterday), licensed Apache-2.0. It adds 57 tokens to every session and 3,100 once invoked, about $0.0002 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
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
merge-queue
Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.
feedback-resolution
Address PR review feedback through surgical fixes traceable to specific comments, apply the Boy Scout Rule only to already-modified files (separate improve: commits), recover context by code snippet rather than line number, and enforce pushback only when factually incorrect, test-breaking, or CLAUDE.md-violating. Use…
pull-request
How to run a pull request to the point where it can be merged — resolving every review conversation, checking every workflow run rather than the summary, and confirming the merge result is what CI actually tested. Load this whenever you open, update, review, or merge a PR, whenever a review round returns findings, and…
resolving-merge-conflicts
Use when you need to resolve an in-progress git merge/rebase conflict.
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.