Borrowing it
Nothing to install: this file belongs to 84emllc/google-calendar-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/84emllc/google-calendar-mcp/main/.claude/commands/review-pr.mdgit clone --depth 1 https://github.com/84emllc/google-calendar-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/commands/84emllc/google-calendar-mcp/review-pr)<a href="https://agentmods.dev/commands/84emllc/google-calendar-mcp/review-pr"><img src="https://agentmods.dev/badge/commands/84emllc/google-calendar-mcp/review-pr/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/commands/84emllc/google-calendar-mcp/review-pr"><img src="https://agentmods.dev/badge/commands/84emllc/google-calendar-mcp/review-pr.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.00016 | $0.00392 |
| Opus 5 | $0.00008 | $0.00196 |
| Sonnet 5 | $0.00003 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
review-pr 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.
This is a copy
100% identical to review-pr — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Review PR $ARGUMENTS for compliance with:
1. MCP Protocol Compliance (mcp-research skill)
Check:
- JSON-RPC 2.0 format correctness
- Capability advertisement accuracy
- Security/consent workflows
- Error handling patterns
- Transport layer compliance
- Production readiness
2. Google Calendar API Best Practices (gcal-api-research skill)
Validate:
- Correct API method usage
- Edge cases handling (recurring events, timezones, all-day events, attendees)
- Error handling for Calendar API failures
- Structured response formats
- Field mask optimization
3. Test Coverage (calendar-test-engineer agent)
Verify:
-
90% code coverage achieved
- Unit tests for all edge cases identified in research
- Integration tests for critical scenarios
- Error path testing
- Mock configurations realistic
Output Format
CRITICAL: BE EXTREMELY CONCISE. MAX 300 WORDS TOTAL.
Audience: Senior engineers with limited time.
DO NOT:
- Create analysis files or documentation
- Write verbose explanations
- Provide code examples unless critical
- List obvious issues
DO:
- Provide file:line references
- Focus on blocking issues only
- Give specific, actionable fixes
MCP Compliance: ✅/⚠️/❌ [one-line summary] Calendar API: ✅/⚠️/❌ [one-line summary] Test Coverage: ✅/⚠️/❌ [coverage % + critical gaps]
Critical Issues: [numbered list, max 3, with file:line] Recommendations: [numbered list, max 3, specific fixes]
Approval Status: APPROVE / REQUEST CHANGES / BLOCK
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 · 61 lines · 16 tokens per session scan A 6b3441c16cb5
review-pr is a command published in the GitHub repository 84emllc/google-calendar-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 392 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to review-pr, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
review
Perform a comprehensive code review with actionable feedback.
conformance
Assess architecture conformance — ADR decision implementation, cross-decision consistency, design-principles alignment, architecture drift, technical debt, and custom constraint rules.
show_diff
Call the showdiff MCP tool to show me a side-by-side visual diff (it returns an image in the chat). If I passed a checkpoint sha in $ARGUMENTS, diff that checkpoint; otherwise show my current uncommitted changes.
dld-review
Review Detailed Design (DLD) for implementation readiness.
refactor-clean
Safely identify and remove dead code with test verification at every step.
review-pr
You MUST review PR $ARGUMENTS right now. Do NOT ask for more information — execute all steps immediately.