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.02585 |
| Opus 5.5 | $0.00006 | $0.01034 |
| Sonnet 5.5 | $0.00003 | $0.00517 |
| Haiku 4.5 | $0.00002 | $0.00259 |
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 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 — 203 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, and keep thehead_shathatgithub_get_pr_contentreports - Read what is already there - call
github_list_pr_reviewsfor the verdicts already given, andgithub_list_pr_commentswithkind="inline"so a second review does not repeat the first - Post inline comments - call
github_add_inline_pr_commentonce per line needing feedback, passing thathead_shaasexpected_head_sha. Each one is published at once as a review of its own, not held for the decision - Post a general comment - optionally call
github_add_pr_commentsfor remarks not tied to a line - Submit the decision - call
github_submit_reviewwithAPPROVE,REQUEST_CHANGESorCOMMENTand the sameexpected_head_sha, leavingbodyunset on an approval
Correcting a comment
- Call
github_list_pr_commentsto find the comment and itsid - Call
github_update_pr_commentwith thatidand the samekindthe listing used - Reply on a thread with
github_reply_to_review_commentrather than opening a new one
Tool Parameters
github_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 the comment ends on, in the file as side sees it |
comment_body |
str | Markdown comment text |
side |
str | RIGHT for an added or context line, LEFT for a deleted one. Default RIGHT |
start_line |
int | None | First line of a range ending at line. Omit to comment on line alone |
start_side |
str | None | Side start_line sits on. Omit to match side |
expected_head_sha |
str | None | Attach the comment to this SHA, as github_get_pr_content reports it. Omit for the current head |
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 Changed · +12 lines 1fbc9417f9c2
- 10d ago Changed · +9 lines f525ae0a7eb4
- 14d ago Changed · +2 lines a3c67c7fb325
- 1mo ago Changed · +37 lines 1ed96d2e4b80
- 1mo ago Changed · +11 lines aec9485fd4b7
- 1mo 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 today), licensed Apache-2.0. It adds 16 tokens to every session and 2,585 once invoked, about $0.0001 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-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.
git-workflow
Branching and review conventions.
watch
Watch live IDX turnover and order books for unusual activity — value surges, auto-reject approach, one-sided depth, walls appearing or withdrawn, quiet stocks waking up, UMA flags — plus delayed print-by-print attribution and end-of-day broker context. Use when the user runs /watch, or asks what is trading right now…
git-workflow
Follow this team's Git conventions for branching, commit messages, and pull requests.
stockbit-status
Check whether the Stockbit session is still valid — main session expiry, whether trading credentials are stored, and the current trading mode. Use when the user asks "am I still logged in to Stockbit", "has my session expired", "is trading on", or when a stockbit MCP tool starts failing with an auth error.
stockbit-auth
Log in to Stockbit and capture the session for this server — opens the browser login flow and verifies the token was stored. Use when the user asks to log in or re-authenticate to Stockbit, or after a status check reports the session expired, HTTP 401, or logged out.