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/saidsef/mcp-github-pr-issue-analyser/pr-analysisnpx skills add saidsef/mcp-github-pr-issue-analyser --skill pr-analysisgit 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-analysis)<a href="https://agentmods.dev/skills/saidsef/mcp-github-pr-issue-analyser/pr-analysis"><img src="https://agentmods.dev/badge/skills/saidsef/mcp-github-pr-issue-analyser/pr-analysis.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 | $0.00018 | $0.01366 |
| Opus 5 | $0.00009 | $0.00683 |
| Sonnet 5 | $0.00004 | $0.00273 |
| Haiku 4.5 | $0.00002 | $0.00137 |
Grade A, and why
pr-analysis 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 5d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Analysis
Read-only inspection of a pull request: what it changes, what it closes, and whether CI is green.
Prerequisites
repo_owner,repo_nameandpr_numberfor the target PR- GitHub token with
reporead access
Workflow
- Fetch metadata - call
get_pr_contentfor title, description, author, state and timestamps - Fetch the diff - call
get_pr_difffor the raw unified diff of every changed file - Fetch linked issues - call
get_pr_linked_issuesto see what merging will auto-close - Fetch CI status - call
get_pr_status_checksto see whether the head commit is green - Synthesise - combine the four into a structured analysis
Steps 3 and 4 do not depend on steps 1 and 2, so issue them together.
Tool Parameters
All four tools take the same three arguments.
| Parameter | Type | Description |
|---|---|---|
repo_owner |
str | GitHub organisation or username |
repo_name |
str | Repository name |
pr_number |
int | Pull request number |
get_pr_content
Returns PRContent with exactly these fields:
| Field | Type | Description |
|---|---|---|
title |
str | PR title |
description |
str | None | PR body in Markdown |
author |
str | Login of the PR author |
created_at |
str | ISO 8601 timestamp |
updated_at |
str | ISO 8601 timestamp |
state |
str | open or closed |
Nothing else is returned. Draft status, base and head refs, labels and
mergeable are not available from this tool. state is closed for both
merged and abandoned PRs and does not distinguish the two.
To learn whether a PR is a draft, call list_open_issues_prs with
filtering="repo" and read is_draft on the matching entry.
get_pr_diff
| Parameter | Type | Default | Description |
|---|---|---|---|
repo_owner |
str | - | GitHub organisation or username |
repo_name |
str | - | Repository name |
pr_number |
int | - | Pull request number |
max_bytes |
int | 131072 |
Cap on the patch returned. 0 asks the size without reading the 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.
- 5d ago First seen · 131 lines · 18 tokens per session scan A 81fbb3378e06
pr-analysis is a skill published in the GitHub repository saidsef/mcp-github-pr-issue-analyser (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,366 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.
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).
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
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.
resolve-pr-comments-stack
Resolve unresolved PR review comments across an entire Graphite (gt) stack of many PRs, bottom-up, in one working directory. Use when asked to "go through this stack and resolve comments", "clean up review comments across the whole stack", or given a list/range of PR numbers that form (or partially form) a gt stack.…
split-commit-into-stack
Split one oversized commit or branch into a stack of independently reviewable Graphite (gt) PRs - deciding what genuinely separates, what is atomic and must stay whole, and proving each lower PR builds and passes without the ones above it. Use when asked to "split this PR", "this commit is too big", "break this into a…