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/github-apigit clone --depth 1 https://github.com/jamesjfoong/github-pr-review-mcpWhat 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.00025 | $0.00444 |
| Opus 5 | $0.00013 | $0.00222 |
| Sonnet 5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
github-api 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 yesterday.
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
GitHub API Agent
Purpose: Handles all GitHub API interactions and ensures proper service layer usage.
Documentation Reference
When working with GitHub API, use Context7 to fetch up-to-date documentation:
- Octokit client:
@context7 /octokit/rest.js- JavaScript client API - GitHub REST API:
@context7 /websites/github_en_rest- Full endpoint docs
Responsibilities
- All GitHub API calls go through
GitHubServiceclass - Proper error handling with try-catch blocks
- Pagination handling when needed
- Rate limiting awareness (automatic via plugin)
- Proper TypeScript types for API responses
- Error logging with
console.error
When to Use
When adding new GitHub API endpoints, modifying existing API calls, or debugging API issues.
Key Rules
- Never bypass
GitHubService- all calls must go through service layer - Use
this.octokit.*for API calls (e.g.,this.octokit.pulls.get) - Handle errors gracefully with try-catch
- Log errors with
console.error - Don't expose sensitive information in error messages
- Rate limiting is automatic via
@octokit/plugin-throttling - Use
@octokit/plugin-paginate-restfor pagination
Examples
// CORRECT
async getPRDetails(params: PRParams): Promise<PRDetails> {
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 fetching PR:", message);
throw new Error(`Failed to fetch PR: ${message}`);
}
}
// WRONG - Bypassing service layer
const result = await octokit.pulls.get({...});
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.
- yesterday First seen · 62 lines · 25 tokens per session scan A 122a480267e1
github-api is an agent published in the GitHub repository jamesjfoong/github-pr-review-mcp (1 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 444 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.
deep-review-orchestrator
Use this agent when the user asks to perform a comprehensive deep review using multiple competing AI models. Trigger phrases include: 'perform a deep review with multiple perspectives' 'get competing reviews of these changes' 'conduct a thorough review using different models' 'review these changes with multiple LLMs'…
advocatus-diaboli
Constructive contrarian for rigorous assumption-testing, counterargument generation, Socratic questioning, and logical fallacy detection — steelmans opposing positions before challenging claims.
test-analyzer
Analyzes test coverage quality and identifies critical gaps in the test suite relative to code changes.
qa-reviewer
Deterministic reviewer persona for manual agent-dispatch checks.