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/anchildress1/awesome-github-copilot/pr-comment-reviewnpx skills add anchildress1/awesome-github-copilot --skill pr-comment-reviewgit clone --depth 1 https://github.com/anchildress1/awesome-github-copilotWrote 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/anchildress1/awesome-github-copilot/pr-comment-review)<a href="https://agentmods.dev/skills/anchildress1/awesome-github-copilot/pr-comment-review"><img src="https://agentmods.dev/badge/skills/anchildress1/awesome-github-copilot/pr-comment-review.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.00162 | $0.02525 |
| Opus 5 | $0.00081 | $0.01262 |
| Sonnet 5 | $0.00032 | $0.00505 |
| Haiku 4.5 | $0.00016 | $0.00252 |
Grade A, and why
pr-comment-review 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remediation workflow for an existing PR. Bot threads rot: unresolved thread, PR merges, the "minor" finding was the real one. Every step below exists to close that gap.
GitHub MCP tools are preferred when loaded
(ToolSearch("select:mcp__plugin_github_github__pull_request_read")); gh api equivalents are
given inline.
1. Resolve the PR
Given a number/URL, use it. Otherwise:
gh pr view --json number,title,body,url,isDraft,baseRefName,headRefName
owner/repo come from whichever identified the PR. A supplied URL carries its own
owner/repo — parse them from it, because the PR may live in a repo the current checkout isn't
(same number, different repo, and every read and reply would land on a stranger's PR). Fall back
to git remote -v (origin) only for a bare number or the current-branch case.
No open PR for the branch → say so and stop. Don't guess.
2. Confirm both required bots reviewed
- Copilot:
copilot-pull-request-reviewer[bot] - Codex:
chatgpt-codex-connector[bot]
pull_request_read(method="get_reviews" | "get_comments", owner, repo, pullNumber)
# gh api --paginate repos/{owner}/{repo}/pulls/{pr}/reviews | .../issues/{pr}/comments
Read every page before concluding anyone is absent. gh api returns one page by default, so a
bot that reviewed after 30 other events looks missing without --paginate; the MCP tool pages
via perPage + the after cursor from pageInfo.
A missing bot is a diagnosis, not a shrug. Diagnose per bot — they have independent configurations, so one explanation rarely covers both:
-
Draft PR — check
isDraft. This only explains Copilot if the repo has not enabled Review draft pull requests in its ruleset; with that on, a draft is no explanation at all and you need a different cause. -
Pending — last push minutes ago; report the timestamp instead of "absent".
-
No prior review history — check whether the bot has ever commented on any PR here:
gh api -X GET search/issues -f q="repo:{owner}/{repo} commenter:app/{bot-slug}" --jq '.total_count'
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 · 217 lines · 162 tokens per session scan A ff5cd5c8f82d
pr-comment-review is a skill published in the GitHub repository anchildress1/awesome-github-copilot (65 stars, last pushed 3d ago), licensed MIT. It adds 162 tokens to every session and 2,525 once invoked, about $0.0008 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
GitHub Copilot Testing Patterns
Effective patterns for using GitHub Copilot to generate, refactor, and maintain test code including prompt engineering for test generation, Copilot Chat for debugging, inline suggestions for assertions, and workspace context optimization.
mcp-server-dev
Use when the user asks to build an MCP server, create an MCP integration, wrap an API for AI agents, or expose tools via the Model Context Protocol. Guides through deployment model selection (remote HTTP, MCPB, local stdio), tool-design patterns, and framework choice before scaffolding code.
conventions-improver
Audit and improve project conventions files (AGENTS.md, CLAUDE.md, GEMINI.md). Scans for all conventions files, evaluates quality against a scoring rubric, outputs a quality report, then makes targeted improvements with user approval. Use when asked to check, audit, update, or improve AGENTS.md or similar files.
security-threat-model
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling.…
code-review
Multi-agent code review for local changes, files, or directories. Detects bugs, security issues, and conventions-file violations (AGENTS.md/CLAUDE.md/GEMINI.md).
gh-address-comments
Fetch all review comments and threads on the current branch's open GitHub PR using the gh CLI, present a numbered summary, and address the ones the user selects.