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 cxcscmu/SkillLearnBench --skill gh-cli-pr-statsgit clone --depth 1 https://github.com/cxcscmu/SkillLearnBenchWrote 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/cxcscmu/skilllearnbench/gh-cli-pr-stats)<a href="https://agentmods.dev/skills/cxcscmu/skilllearnbench/gh-cli-pr-stats"><img src="https://agentmods.dev/badge/skills/cxcscmu/skilllearnbench/gh-cli-pr-stats.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.00026 | $0.00430 |
| Opus 5 | $0.00013 | $0.00215 |
| Sonnet 5 | $0.00005 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
gh-cli-pr-stats 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 3d 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
PR Statistics from gh CLI Output
Fetching PR Data with Timestamps
gh pr list --repo owner/repo --state all \
--search "created:2024-12-01..2024-12-31" \
--limit 500 \
--json number,state,author,createdAt,mergedAt
The author field returns an object: {"login": "username"}.
The state field returns: OPEN, CLOSED, or MERGED.
Computing Average Merge Time with jq
# Filter merged PRs and compute average days to merge
echo "$pr_json" | jq '
[.[] | select(.state == "MERGED") |
{ created: (.createdAt | fromdateiso8601),
merged: (.mergedAt | fromdateiso8601) } |
(.merged - .created) / 86400
] | add / length
'
fromdateiso8601converts ISO 8601 strings to Unix epoch seconds.- Divide difference by 86400 to get days.
add / lengthcomputes the mean.
Finding Top Contributor
echo "$pr_json" | jq '
group_by(.author.login) |
map({login: .[0].author.login, count: length}) |
sort_by(-.count) |
.[0]
'
Counting by State
echo "$pr_json" | jq '{
total: length,
merged: [.[] | select(.state == "MERGED")] | length,
closed: [.[] | select(.state == "CLOSED")] | length
}'
Note: In gh CLI output, CLOSED and MERGED are distinct states. A merged PR has state MERGED, not CLOSED.
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.
- 3d ago First seen · 59 lines · 26 tokens per session scan A 5e292fabea3b
gh-cli-pr-stats is a skill published in the GitHub repository cxcscmu/SkillLearnBench (83 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 430 once invoked, about $0.0001 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 skills, from other repositories
syncing-memory-filesystem
Diagnose and repair MemFS repository setup, remote sync, authentication failures, optional backup remotes, or merge/rebase conflicts. Do not load for routine memory reads or edits.
hotpath_bump
Bump the hotpath version number across the workspace and related files. Updates crate versions in Cargo.toml files (exact patch version) and version references in the backend middleware, hotpathinit skill, and README (major.minor only). Use when the user wants to bump, bump the version, or release a new hotpath…
parallel-pr-review
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
github
GitHub API integration via HTTP tool with automatic credential injection.
review-readiness
PR readiness dashboard — tracks which reviews have been completed per branch and gates merge decisions. Shows code review, tests, security, QA, and linting status.
project-setup
Add a GitHub repository as a tracked project — creates workspace entity, installs workflow automation missions, and includes in dev brief scope.