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/code-analyzergit 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.00023 | $0.00291 |
| Opus 5 | $0.00012 | $0.00146 |
| Sonnet 5 | $0.00005 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
code-analyzer 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
Code Analyzer Agent
Purpose: Maintains and extends the code analysis engine.
Responsibilities
- Add new analysis patterns to
CodeAnalyzerclass - Keep analyzers pure (no side effects)
- Return structured results:
{ issues, suggestions, metrics } - Security pattern detection
- Code smell detection
- Quality metrics calculation
When to Use
When adding new analysis features, improving existing analyzers, or fixing analysis bugs.
Key Rules
- Keep
CodeAnalyzerpure - no side effects - Return structured results with
issues,suggestions, andmetrics - Add patterns to appropriate arrays (security, code smells, etc.)
- Test analyzers with various code samples
- Patterns should be regex-based for code scanning
Examples
// ✅ CORRECT
analyze(files: CodeFile[]): AnalysisResult {
const issues: CodeIssue[] = [];
// Pure function - no side effects
// Returns structured result
return { issues, suggestions, metrics };
}
// ❌ WRONG - Side effects
analyze(files: CodeFile[]): AnalysisResult {
console.log("Analyzing..."); // Side effect
this.cache = files; // Side effect
return { issues: [] };
}
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 · 49 lines · 23 tokens per session scan A 290089302cc3
code-analyzer 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 291 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.