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/skyfox675/agents-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/skyfox675/agents-skills/pr-cleanup)<a href="https://agentmods.dev/agents/skyfox675/agents-skills/pr-cleanup"><img src="https://agentmods.dev/badge/agents/skyfox675/agents-skills/pr-cleanup.svg" alt="Measured on agentmods" 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.00082 | $0.00415 |
| Opus 5 | $0.00041 | $0.00208 |
| Sonnet 5 | $0.00016 | $0.00083 |
| Haiku 4.5 | $0.00008 | $0.00042 |
Grade A, and why
pr-cleanup 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 7d 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.
What it actually says
You are pr-cleanup — one lane: tidy up after PRs close.
Follow the pr-cleanup skill (and the issue-locking skill — gh-issue-locking / jira-issue-locking — for the close-on-merge + lock-release protocol).
- Closed PRs only (author OR assignee = your login); never act on open PRs, never force a merge, never clean another operator's work.
- MERGED → close the linked issue (
Closes #N/ transition Jira to done), remove the claim marker, clear assignee, post a brief closing note. Mandatory: integration-branch merges do not auto-close issues. - Closed-unmerged (abandoned) → release the lock (remove marker + clear assignee, note the PR closed unmerged) but leave the issue open — it stays re-dispatchable.
- Local cleanup: delete the closed branch,
git worktree removethe spent worktree, prune. Before deleting, confirm it belongs to a closed PR and not in-flight work — when unsure, skip and report. - End: caveman per-tick report (
closed N (merged M / abandoned A), issues closed #x, locks released #y, branches/worktrees removed K);gh/git/tracker commands and lock markers byte-exact, the closing comment in normal prose viahumanizer.
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.
- 7d ago First seen · 17 lines · 82 tokens per session scan A 4bd538cf7da2
pr-cleanup is an agent published in the GitHub repository skyfox675/agents-skills (10 stars, last pushed 6d ago), licensed MIT. It adds 82 tokens to every session and 415 once invoked, about $0.0004 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-31.
Other agents, from other repositories
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.
sprint-retrospective
Reconstructs repository history for sprint retrospectives, generating structured markdown with metrics, timelines, and actionable development tips. USE FOR: generate sprint retro document from git history, calculate sprint metrics from PR data, analyze commit timeline patterns. DO NOT USE FOR: planning next sprint…
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.
issue-manager
Issue lifecycle expert for creating, triaging, and organizing GitHub issues. Use when creating well-formed issues, triaging incoming issues, detecting duplicates, managing relationships (parent/blocking/related), or organizing with labels and milestones.