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/flurdy/agent-skills/pr-statusnpx skills add flurdy/agent-skills --skill pr-statusgit clone --depth 1 https://github.com/flurdy/agent-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/skills/flurdy/agent-skills/pr-status)<a href="https://agentmods.dev/skills/flurdy/agent-skills/pr-status"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/pr-status.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.00033 | $0.03070 |
| Opus 5 | $0.00016 | $0.01535 |
| Sonnet 5 | $0.00007 | $0.00614 |
| Haiku 4.5 | $0.00003 | $0.00307 |
Grade A, and why
pr-status 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Status
Show enriched status for all open PRs created by you across your GitHub org: CI checks, approvals, unresolved review threads, and linked Jira discussion. Also shows recently closed PRs.
The GitHub org is auto-detected from the current repo's origin remote, falling back to the most common org across a multi-repo workspace's member repos when the cwd repo has no GitHub remote of its own (a workspace root is often deliberately local-only). Override via the PR_STATUS_ORG env var or a first positional argument. When nothing resolves the scripts exit non-zero with an explanatory message rather than returning an empty list.
The output of this skill is the rendered dashboard (steps 3–6). Fetching without rendering is not a valid run.
Usage
/pr-status
Instructions
Re-run the fetch scripts and date on every invocation, even seconds after the last one — never reuse earlier output or extrapolate the timestamp.
1. Fetch
Open PRs (org-wide), one JSON object per line {number, title, owner, repo}:
~/.agents/skills/pr-status/scripts/gh-pr-list-open.sh
Recently closed PRs (3-day lookback, 4 on Tuesdays; optional second arg overrides), one JSON object per line {number, title, owner, repo, closedAt}:
~/.agents/skills/pr-status/scripts/gh-pr-list-closed.sh
2. Fetch PR details
Group the PRs (open and closed) by owner/repo; one batch GraphQL call per group:
~/.agents/skills/pr-status/scripts/gh-pr-details.sh {owner} {repo} {number1} {number2} ...
Output is a JSON array, one object per PR:
[
{
"number": 123,
"base": "main",
"isDraft": false,
"mergeState": "CLEAN",
"reviewDecision": "APPROVED",
"approvers": ["alice"],
"unresolvedThreads": 2,
"checksState": "SUCCESS",
"lastPush": "2026-04-15T09:30:00Z",
"mergeCommitSha": "abc123...",
"mergeCommitAt": "2026-04-15T10:00:00Z",
"mainChecksState": "SUCCESS",
"readyAt": "2026-04-14T15:32:11Z"
}
]
What ships with it
19 files 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.
- scripts/gh-pr-checkout.py 17 KB runs code
- scripts/gh-pr-checks.sh 127 B runs code
- scripts/gh-pr-details.sh 1.8 KB runs code
- scripts/gh-pr-feedback.py 33 KB runs code
- scripts/gh-pr-list-closed.sh 1.5 KB runs code
- scripts/gh-pr-list-open.sh 435 B runs code
- scripts/gh-pr-merge-state.sh 154 B runs code
- scripts/gh-pr-review-requests.py 51 KB runs code
- scripts/gh-pr-reviews.sh 192 B runs code
- scripts/gh-pr-threads.sh 406 B runs code
- scripts/resolve-org.sh 2.7 KB runs code
- tests/fixtures/all-sources.json 6.7 KB
- tests/fixtures/edited-comment.json 140 B
- tests/fixtures/pagination.json 2.2 KB
- tests/fixtures/partial-failure.json 1.3 KB
- tests/test_checkout_resolver.py 11 KB runs code
- tests/test_feedback_inventory.py 16 KB runs code
- tests/test_review_request_queue.py 34 KB runs code
- tests/test-feedback-contract.sh 1.3 KB runs code
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 · 205 lines · 33 tokens per session scan A 26a1281fe816
pr-status is a skill published in the GitHub repository flurdy/agent-skills (8 stars, last pushed 7d ago), licensed MIT. It adds 33 tokens to every session and 3,070 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…