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 agentmods add skills/github/gh-aw/github-pr-querynpx skills add github/gh-aw --skill github-pr-querygit clone --depth 1 https://github.com/github/gh-awWhat 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 | $0.00016 | $0.00926 |
| Opus 5 | $0.00008 | $0.00463 |
| Sonnet 5 | $0.00003 | $0.00185 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
github-pr-query 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 2d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Pull Request Query Skill
Query GitHub pull requests efficiently with built-in jq filtering.
Important: jq Parameter is Optional
The --jq parameter is optional. Without --jq, this skill returns schema and data size information instead of full data.
Use this to avoid oversized responses and inspect structure before targeted queries.
Use --jq '.' to get all data, or use a more specific filter for targeted results.
Usage
Use this skill to query pull requests from the current repository or any specified repository.
Basic Query (Returns Schema Only)
To list pull requests from the current repository:
./query-prs.sh
# Returns schema and data size, not full data
Get All Data
To get all PR data:
./query-prs.sh --jq '.'
With Repository
To query a specific repository:
./query-prs.sh --repo owner/repo
With jq Filtering
Use the --jq argument to filter and transform the output:
# Get only open PRs
./query-prs.sh --jq '.[] | select(.state == "open")'
# Get PR numbers and titles
./query-prs.sh --jq '.[] | {number, title}'
# Get PRs by a specific author
./query-prs.sh --jq '.[] | select(.author.login == "username")'
# Get merged PRs from last week
./query-prs.sh --jq '.[] | select(.mergedAt != null)'
# Count PRs by state
./query-prs.sh --jq 'group_by(.state) | map({state: .[0].state, count: length})'
Common Options
--state: Filter by state (open, closed, merged, all). Default: open--limit: Maximum number of PRs to fetch. Default: 30--repo: Repository in owner/repo format. Default: current repo--author: Filter PRs by author login--app: Filter PRs by GitHub App author--search: Apply GitHub issue/PR search syntax--jq: (Optional) jq expression for filtering/transforming output. If omitted, returns schema info
Example Queries
Find large PRs (many changed files):
./query-prs.sh --jq '.[] | select(.changedFiles > 10) | {number, title, changedFiles}'
What ships with it
1 file 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.
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.
- 2d ago First seen · 120 lines · 16 tokens per session scan A 19f63c4bdc30
github-pr-query is a skill published in the GitHub repository github/gh-aw (5,050 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 926 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-08-30.
Other skills, from other repositories
c-github
Interact with GitHub using the gh CLI and jq. Manage PRs, issues, repositories, and Actions workflows. Make raw API calls with gh api for anything not covered by built-in commands.
watch-pr
Watch a GitHub pull request for CI status, reviews, comments, merge conflicts, and terminal states using the gh-watch extension. Use when the user wants to monitor a PR, wait for CI, or track PR progress.
watch-tag
Watch a GitHub repository for new tags using the gh-watch extension. Use when the user wants to be notified when a tag is created, when a release is cut, or when a tag that includes a specific commit appears (e.g. "tell me when my merge ships in a release").
watch-branch
Watch a GitHub branch for new commits using the gh-watch extension. Use when the user wants to be notified when new commits are pushed to a branch, monitor main for merges, or track branch activity.
watch-commit
Watch a GitHub commit for CI status changes using the gh-watch extension. Use when the user wants to monitor a commit's CI checks, wait for a build to finish, or track CI progress on a specific SHA.
update-architecture-docs
Generate or update the architecture documentation in docs/content/architecture/. Use on "update architecture docs", "generate architecture documentation", "regenerate architecture docs", or after any structural change to the codebase.