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 agents/jamesjfoong/github-pr-review-mcp/mcp-toolgit 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/agents/jamesjfoong/github-pr-review-mcp/mcp-tool)<a href="https://agentmods.dev/agents/jamesjfoong/github-pr-review-mcp/mcp-tool"><img src="https://agentmods.dev/badge/agents/jamesjfoong/github-pr-review-mcp/mcp-tool.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.1 | $0.00023 | $0.00403 |
| Opus 5 | $0.00012 | $0.00201 |
| Sonnet 5 | $0.00005 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
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 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.
What it actually says
MCP Tool Agent
Purpose: Manages MCP tool registration and ensures proper tool structure.
Responsibilities
- Follow 3-step process for adding tools (schema → service → registration)
- Ensure proper tool descriptions
- Verify parameter schemas match service method parameters
- Check tool responses are properly formatted
- Update README.md tool table when adding tools
When to Use
When adding new MCP tools, modifying existing tools, or debugging tool issues.
Key Rules
- Define schema in
src/types.ts - Add service method in
src/github-service.ts - Register tool in
src/index.ts - Update README.md tool table
- Export both schema and type from
types.ts
3-Step Process
Step 1: Define Schema (src/types.ts)
export const NewToolSchema = z.object({
owner: z.string().describe("Repository owner"),
repo: z.string().describe("Repository name"),
});
// Explicit type (preferred over z.infer<typeof>)
export interface NewToolParams {
owner: string;
repo: string;
prNumber: number;
}
Step 2: Add Service Method (src/github-service.ts)
async newMethod(params: NewToolParams): Promise<ResultType> {
// Implementation using this.octokit
}
Step 3: Register Tool (src/index.ts)
server.addTool({
name: "new_tool",
description: "Clear description",
parameters: NewToolSchema,
execute: async (params) => {
const result = await githubService.newMethod(params);
return {
content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
};
},
});
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 · 70 lines · 23 tokens per session scan A 44b09efe5991
mcp-tool is an agent published in the GitHub repository jamesjfoong/github-pr-review-mcp (1 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 403 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 agents, from other repositories
dev
开发者(Developer)角色:负责代码实现、PR 创建与迭代、代码审查响应、 技术方案设计。监听 issues.assigned 事件,自动接收被指派的开发任务。.
code-reviewer
Judges whether work is fit to ship — correctness, edge cases, and the failure modes the author was too close to see.
skill-reviewer
Skill quality reviewer for SKILL.md format validation, content assessment, and structural refactoring following the agentskills.io standard.
qa-reviewer
Deterministic reviewer persona for manual agent-dispatch checks.
code-reviewer
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
AGENTS
Subagent contracts. Each .md is a system prompt with enforced YAML frontmatter.