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 systemfsoftware/comment-checker --skill pr-queuegit clone --depth 1 https://github.com/systemfsoftware/comment-checkerWrote 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/systemfsoftware/comment-checker/pr-queue)<a href="https://agentmods.dev/skills/systemfsoftware/comment-checker/pr-queue"><img src="https://agentmods.dev/badge/skills/systemfsoftware/comment-checker/pr-queue/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/systemfsoftware/comment-checker/pr-queue"><img src="https://agentmods.dev/badge/skills/systemfsoftware/comment-checker/pr-queue.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.00161 | $0.04264 |
| Opus 5.5 | $0.00064 | $0.01706 |
| Sonnet 5.5 | $0.00032 | $0.00853 |
| Haiku 4.5 | $0.00016 | $0.00426 |
Grade A, and why
pr-queue 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 — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull request queue
This session is a queue. Build the catalog once, then take one PR at a time: fix it, push it, and ask the user to merge or close it. The user merges; you never do.
1. Build the catalog and shortlist
Turn the user's criteria into a search. An area like docker or cloudflare
matches conventional-commit scopes (feat(docker), fix(cloudflare/r2)!) and
PRs that touch that provider's paths.
gh pr list --state open --limit 300 --json number,title,author,isDraft,mergeable,additions,deletions,changedFiles,updatedAt,isCrossRepository,maintainerCanModify,headRefName,baseRefName,url \
> /tmp/pr-queue.json
# scope match: ^\w+!?\((<area>)(/[^)]*)?\)!?: (case-insensitive)
# path match for anything the title missed:
gh pr view <n> --json files --jq '.files[].path' | grep -i '<Area>/'
For issues use gh issue list --state open --search "<area> in:title,body".
Free-form criteria map onto --author, --label, --search. Leave out the
user's own PRs unless asked, and honor any exclusions they give (e.g. "ignore
the container PRs").
Print the catalog, grouped by theme when it's large:
PR (link) | Author | Size | Behind main | What it does | Audit notes, with
✅/❌ against the standards in §3. Annotate:
- stacks — a PR whose
baseRefNameis another PR's branch (base #N ← child #M) - overlaps — PRs fixing the same issue or touching the same files; plan a merge order and which ones to close
- drafts, and PRs waiting on the author's answer to an earlier question
Then the shortlist: top 10, easiest first —
# | PR (link) | Author | Size | Tests now | Likely work. Rank by clean merge,
small diff, tests already in the right shape, single concern. Exclude drafts,
PRs waiting on the author, and forks we can't push to
(maintainerCanModify: false). PRs needing a test rewrite go on a separate
rework list. If fewer than 10 match, say it's the whole list.
Keep the shortlist as a status table (todo / ready → merge? / close? /
merged / closed / parked) and re-print it whenever it changes. When it's
exhausted, re-run the search for the next 10.
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 · 330 lines · 0 tokens per session scan A e54b9f7cf905
pr-queue is a skill published in the GitHub repository systemfsoftware/comment-checker (4 stars, last pushed 6d ago), licensed Apache-2.0. It adds 161 tokens to every session and 4,264 once invoked, about $0.0006 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-10-19.
Other skills, from other repositories
issue-sdlc
Take ONE open GitHub issue through the full delivery lifecycle — triage, plan, implement in a worktree, QA, review, merge, then comment and close. Trigger on "process an issue", "work the issue backlog", or an hourly issue-sdlc cron tick.
fix-issue
Use when the user wants to fix a GitHub issue by number, resolve a bug report, or close an issue.
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
github-monitor
Watch your GitHub repos across four views - a combined urgency monitor (stale PRs, new issues, releases), a new-issue triage queue, a release upgrade digest, or your own opened-PR tracker.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.