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 github-api-paginationgit 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/github-api-pagination)<a href="https://agentmods.dev/skills/cxcscmu/skilllearnbench/github-api-pagination"><img src="https://agentmods.dev/badge/skills/cxcscmu/skilllearnbench/github-api-pagination.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.00030 | $0.00741 |
| Opus 5 | $0.00015 | $0.00370 |
| Sonnet 5 | $0.00006 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
github-api-pagination 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub API Pagination with gh api
Overview
GitHub REST API returns paginated results (default 30, max 100 per page). Use gh api with --paginate to automatically fetch all pages.
Basic Usage
# Fetch all pages automatically
gh api --paginate /repos/OWNER/REPO/pulls \
-X GET \
-f state=all \
-f per_page=100
# Use GraphQL for complex queries (no pagination needed for small sets)
gh api graphql -f query='...'
REST API: List PRs with Date Filtering
# Get all PRs created in December 2024 (state=all includes open/closed/merged)
gh api --paginate \
"repos/cli/cli/pulls?state=all&per_page=100&sort=created&direction=desc" \
--jq '.[] | select(.created_at >= "2024-12-01T00:00:00Z" and .created_at < "2025-01-01T00:00:00Z")'
Note:
--jqapplies a jq filter to each page's output.
REST API: List Issues with Date Filtering
gh api --paginate \
"repos/cli/cli/issues?state=all&per_page=100&sort=created&direction=desc" \
--jq '.[] | select(.pull_request == null)' # exclude PRs from issues endpoint
Search API (Efficient for Date Ranges)
The Search API is better for date-bounded queries:
# PRs created in Dec 2024
gh api --paginate \
"search/issues?q=repo:cli/cli+is:pr+created:2024-12-01..2024-12-31&per_page=100" \
--jq '.items[]'
# Issues created in Dec 2024
gh api --paginate \
"search/issues?q=repo:cli/cli+is:issue+created:2024-12-01..2024-12-31&per_page=100" \
--jq '.items[]'
Combining Pages into a Single JSON Array
# Collect all pages into a single JSON array using --paginate + jq slurp
gh api --paginate \
"repos/cli/cli/pulls?state=all&per_page=100" \
--jq '.[]' | jq -s '.'
Key Fields
| Field | Description |
|---|---|
created_at |
ISO8601 timestamp when PR/issue was created |
merged_at |
ISO8601 timestamp when PR was merged (null if not merged) |
closed_at |
ISO8601 timestamp when PR/issue was closed |
state |
open, closed |
pull_request.merged_at |
For search API results |
labels[].name |
Array of label objects with name field |
user.login |
Author's GitHub username |
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 · 86 lines · 30 tokens per session scan A 0e55a73c73cc
github-api-pagination is a skill published in the GitHub repository cxcscmu/SkillLearnBench (83 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 741 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 skills, from other repositories
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…
scope-creep-detector
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad pull requests, changes that grew beyond a fix, dependency additions, public API renames, config or CI edits, oversized hunks, and formatting-only files. Use when the user asks whether a change grew beyond the fix, a PR is too…
prowler-changelog
Manages changelog entries for Prowler components following keepachangelog.com format. Trigger: When creating PRs, adding changelog entries, or working with any CHANGELOG.md file in ui/, api/, mcpserver/, or prowler/.
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.
project-setup
Add a GitHub repository as a tracked project — creates workspace entity, installs workflow automation missions, and includes in dev brief scope.