Borrowing it
Nothing to install: this file belongs to jamesjfoong/github-pr-review-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jamesjfoong/github-pr-review-mcp/main/.cursor/skills/add-mcp-tool/SKILL.mdgit clone --depth 1 https://github.com/jamesjfoong/github-pr-review-mcpWrote 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/jamesjfoong/github-pr-review-mcp/add-mcp-tool)<a href="https://agentmods.dev/skills/jamesjfoong/github-pr-review-mcp/add-mcp-tool"><img src="https://agentmods.dev/badge/skills/jamesjfoong/github-pr-review-mcp/add-mcp-tool/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/jamesjfoong/github-pr-review-mcp/add-mcp-tool"><img src="https://agentmods.dev/badge/skills/jamesjfoong/github-pr-review-mcp/add-mcp-tool.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.00023 | $0.00401 |
| Opus 5 | $0.00012 | $0.00200 |
| Sonnet 5 | $0.00005 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
add-mcp-tool 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.
What it actually says
Add MCP Tool
When to Use
When adding a new GitHub PR review capability to the MCP server.
Steps
1. Define Schema (src/types.ts)
// Schema for runtime validation
export const NewToolSchema = z.object({
owner: z.string().describe("Repository owner/organization"),
repo: z.string().describe("Repository name"),
prNumber: z.number().describe("Pull request number"),
});
// Explicit type definition (preferred)
export interface NewToolParams {
owner: string;
repo: string;
prNumber: number;
}
2. Add Service Method (src/github-service.ts)
async newMethod(params: NewToolParams): Promise<ResultType> {
try {
const result = await this.octokit.pulls.get({
owner: params.owner,
repo: params.repo,
pull_number: params.prNumber,
});
return result.data;
} catch (error) {
const message = error instanceof Error ? error.message : String(error);
console.error("Error in newMethod:", message);
throw new Error(`Failed to execute newMethod: ${message}`);
}
}
3. Register Tool (src/index.ts)
server.addTool({
name: "new_tool_name",
description: "Clear description of what this tool does",
parameters: NewToolSchema,
execute: async (params: NewToolParams) => {
const result = await githubService.newMethod(params);
return {
content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
};
},
});
4. Update Documentation
Update README.md tool table with the new tool.
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 · 70 lines · 23 tokens per session scan A d2a45797d224
add-mcp-tool is a skill published in the GitHub repository jamesjfoong/github-pr-review-mcp (1 stars, last pushed 7mo ago), licensed MIT. It adds 23 tokens to every session and 401 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
pr-description
Write a reviewer-first pull-request description from the actual branch diff. Use when opening a PR or asked to write/improve a PR description.
pr-reviewer
AI-powered pull request review and summarization - analyze diffs, detect bugs, security issues, suggest improvements, generate PR summaries, and auto-comment on GitHub PRs.
ask-copilot
Use GitHub Copilot CLI in non-interactive mode to ask questions, review code, or generate snippets without manual interaction.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
pr
Use when reviewing an incoming GitHub pull request — runs the multi-level (L1-L5) audit against the PR's real diff range, posts findings as one batched review (inline, summary, or local-only), offers the standard fix chain on NEEDSFIX, and optionally merges. The maintainer-side counterpart to /hyperflow:issue. Trigger…
code-review-github
GitHub PR workflow orchestration for code review — list PRs, post comments, apply labels, and guarded auto-merge.