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 jamestexas/agents --skill pr-suggestiongit clone --depth 1 https://github.com/jamestexas/agentsWrote 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/jamestexas/agents/pr-suggestion)<a href="https://agentmods.dev/skills/jamestexas/agents/pr-suggestion"><img src="https://agentmods.dev/badge/skills/jamestexas/agents/pr-suggestion/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jamestexas/agents/pr-suggestion"><img src="https://agentmods.dev/badge/skills/jamestexas/agents/pr-suggestion.svg" alt="Reviewed on agentmods" width="80" 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.00124 | $0.02824 |
| Opus 5.5 | $0.00050 | $0.01130 |
| Sonnet 5.5 | $0.00025 | $0.00565 |
| Haiku 4.5 | $0.00012 | $0.00282 |
Grade A, and why
pr-suggestion 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 1mo 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-suggestion — turn a review finding into a one-click applyable change
The spine, one question:
Is this finding a literal replacement of a line the PR already changed? If yes, post it as a
suggestionso the author applies it with one click. If no, post a described comment — a suggestion here would be broken or wrong.
Posting gate (repo-wide rule, same as pr-review-kit): nothing in this skill is posted to GitHub without explicit human authorization. Prepare the payloads, show what will be posted and where, and call the API only on an explicit go.
A suggestion is a gift when it fits and a trap when it doesn't. A wrong or unappliable suggestion is worse than a clear description: the author clicks "Commit suggestion," gets a broken commit or a no-op, and learns to distrust your review. Match the tool to the finding.
The suggestability decision rule (run this before writing anything)
A finding is suggestable only if all three hold:
- In-diff — the line(s) you'd replace are on the RIGHT side of the diff (added/changed in the PR head). Unchanged context lines cannot host a suggestion at all — the API rejects them.
- Contiguous — the fix is one continuous line range, not edits scattered across the file. A suggestion replaces exactly the anchored range.
- Literal replacement — you can write the full new text for that range. A suggestion is a verbatim swap, not a diff or an instruction.
| Finding shape | Suggestable? | Why |
|---|---|---|
| Wrong constant / operator / off-by-one on a changed line | ✅ yes | literal edit, in-diff, contiguous |
Missing nil/error check right after an added line |
✅ (append trick) | replace the added line with itself + the new line |
| Rename a field the PR introduced | ✅ if contiguous | literal, in-diff |
| Change happens in code the PR didn't touch | ❌ no | not in the diff — nothing to anchor |
| Architectural swap spanning multiple regions | ❌ no | not contiguous |
| Add a whole new function/test out of band | ❌ (usually) | addition, not replacement — describe or hand a patch |
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.
- 1mo ago Changed · +47 lines daf6bf9291ad
- 1mo ago Changed · +26 lines fec64d486ffc
- 1mo ago Changed 4966c88d5642
- 1mo ago First seen · 168 lines · 124 tokens per session scan A 03665bb02385
pr-suggestion is a skill published in the GitHub repository jamestexas/agents (2 stars, last pushed 23d ago), licensed Apache-2.0. It adds 124 tokens to every session and 2,824 once invoked, about $0.0005 per session on Opus 5.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-12.
Other skills, from other repositories
code-review
Review pull requests for repository fit, meaningful value, trustworthy provenance, differentiation, and maintainability in awesome-copilot.
discount-review
Inspect the discount policy fixture with a repeatable review checklist and helper script.
code-review
Reviews code for bugs, security issues, and best practices.
crit-story
Author a crit story and continue the interactive review loop only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
mcp-server-review
Review a Model Context Protocol (MCP) server implementation against the 2026-07-28 protocol revision, which removed the initialize handshake and Mcp-Session-Id and made the protocol stateless. Use when the user asks to review, audit, upgrade or migrate an MCP server, asks whether their MCP server is spec compliant…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…