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 saidsef/mcp-github-pr-issue-analyser --skill pr-reviewgit clone --depth 1 https://github.com/saidsef/mcp-github-pr-issue-analyserWrote 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/saidsef/mcp-github-pr-issue-analyser/pr-review)<a href="https://agentmods.dev/skills/saidsef/mcp-github-pr-issue-analyser/pr-review"><img src="https://agentmods.dev/badge/skills/saidsef/mcp-github-pr-issue-analyser/pr-review/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/saidsef/mcp-github-pr-issue-analyser/pr-review"><img src="https://agentmods.dev/badge/skills/saidsef/mcp-github-pr-issue-analyser/pr-review.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.00016 | $0.01411 |
| Opus 5 | $0.00008 | $0.00705 |
| Sonnet 5 | $0.00003 | $0.00282 |
| Haiku 4.5 | $0.00002 | $0.00141 |
Grade A, and why
pr-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 9d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review
Post targeted inline comments on specific lines, then submit a review decision of approve, request changes, or comment.
Prerequisites
- Read the
pr-analysisskill first and analyse the PR before reviewing it repo_owner,repo_nameandpr_numberfor the target PR- GitHub token with
repowrite access
Workflow
- Analyse the PR - follow the
pr-analysisskill to read the diff, metadata and CI status - Read what is already there - call
list_pr_commentswithkind="inline"so a second review does not repeat the first - Post inline comments - call
add_inline_pr_commentonce per line needing feedback - Post a general comment - optionally call
add_pr_commentsfor remarks not tied to a line - Submit the decision - call
update_reviewswithAPPROVE,REQUEST_CHANGESorCOMMENT
Correcting a comment
- Call
list_pr_commentsto find the comment and itsid - Call
update_pr_commentwith thatidand the samekindthe listing used - Reply on a thread with
reply_to_review_commentrather than opening a new one
Tool Parameters
add_inline_pr_comment
| Parameter | Type | Description |
|---|---|---|
repo_owner |
str | GitHub organisation or username |
repo_name |
str | Repository name |
pr_number |
int | Pull request number |
path |
str | File path relative to repo root, e.g. src/mcp_github/auth.py |
line |
int | Line number in the new file, the right side of the diff |
comment_body |
str | Markdown comment text |
Returns CommentData with id, body, author, html_url, created_at.
The line must fall inside the diff hunks of the PR. GitHub rejects a comment on an unchanged line outside any hunk, and on a path not present in the diff.
add_pr_comments
| Parameter | Type | Description |
|---|---|---|
repo_owner |
str | GitHub organisation or username |
repo_name |
str | Repository name |
pr_number |
int | Pull request number |
comment |
str | Markdown comment text for the PR conversation thread |
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.
- 9d ago First seen · 132 lines · 16 tokens per session scan A 1af0fea06e5e
pr-review is a skill published in the GitHub repository saidsef/mcp-github-pr-issue-analyser (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,411 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-31.
Other skills, from other repositories
atelier
Two-agent post-generation quality gate for vibe-coded applications. Deterministic, gradeable ruleset enforcing UI/UX design-system craft and backend architectural soundness.
wcode
Use the wcode plugin and its MCP tools for repository coding, review, debugging, refactoring, architecture, Graph/Design inspection, safe edits, command execution, and verification. Trigger whenever wcode is installed or named, even when its tools are lazily registered or omitted from the host's initial tool list.
red-blue-review
An optional adversarial review process for requirement analyses. One agent produces the analysis, while an independent reviewer checks its report, database definitions, alignment records, and requirements for missed issues.
mcp-dino
Skill "mcp-dino" from shennawardana23/mcp-dino, covering skill.md — dino-mcp development skills, skill: build & run, quick build (go only, uses existing ui), full build (vite ui + go) and run in dev mode (verbose).
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.