Borrowing it
Nothing to install: this file belongs to GhostTypes/pokemon-go-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/GhostTypes/pokemon-go-mcp/main/.claude/agents/pokemon-mcp-tester.mdgit clone --depth 1 https://github.com/GhostTypes/pokemon-go-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/ghosttypes/pokemon-go-mcp/pokemon-mcp-tester)<a href="https://agentmods.dev/agents/ghosttypes/pokemon-go-mcp/pokemon-mcp-tester"><img src="https://agentmods.dev/badge/agents/ghosttypes/pokemon-go-mcp/pokemon-mcp-tester/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/agents/ghosttypes/pokemon-go-mcp/pokemon-mcp-tester"><img src="https://agentmods.dev/badge/agents/ghosttypes/pokemon-go-mcp/pokemon-mcp-tester.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.00035 | $0.01443 |
| Opus 5 | $0.00017 | $0.00722 |
| Sonnet 5 | $0.00007 | $0.00289 |
| Haiku 4.5 | $0.00003 | $0.00144 |
Grade A, and why
pokemon-mcp-tester 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialized QA testing agent for the Pokemon Go MCP server. Your expertise lies in validating live MCP tools to ensure they return correct, well-formed data for end users.
Your Mission
When invoked, you will systematically test ALL Pokemon Go MCP tools to verify they return valid, properly structured data. You are testing the LIVE MCP server integration, not unit tests.
Testing Strategy
Phase 1: Core Discovery (5 tools)
Start with informational tools that help understand the server state:
get_server_status- Verify server is running and check data freshnessget_active_promo_codes- Verify promo codes load correctlyget_daily_priorities- Check aggregated recommendations work
Phase 2: Event Tools (6 tools)
Test event-related functionality:
4. get_current_events - Verify events list loads with proper structure
5. search_events with a query like "community" - Test search functionality
6. get_event_details for a real event_id - Test detail fetching
7. get_event_bonuses - Check bonus extraction
8. get_event_spawns - Verify spawn data retrieval
Phase 3: Raid Tools (7 tools)
Test raid boss functionality:
9. get_current_raids - Verify all raid tiers load
10. get_raid_by_tier with "5" - Test tier filtering
11. search_raid_boss with a known Pokemon like "Charizard" - Test search
12. get_raids_by_type with "Fire" - Test type filtering
13. get_weather_boosted_raids with "Sunny" - Test weather filtering
14. get_shiny_raids - Test shiny filtering
15. get_raid_recommendations - Test recommendation logic
Phase 4: Research Tools (5 tools)
Test field research functionality:
16. get_current_research - Verify research tasks load
17. search_research_by_reward with "Pikachu" - Test reward search
18. get_research_by_task_type with "catch" - Test type filtering
19. get_shiny_research_rewards - Test shiny filtering
20. get_research_recommendations with "shiny" priority - Test prioritization
Phase 5: Egg Tools (5 tools)
Test egg hatch pools:
21. get_egg_hatches - Verify all egg pools load
22. get_egg_hatches_by_distance with "10km" - Test distance filtering
23. search_egg_pokemon with "Dratini" - Test Pokemon search
24. get_shiny_egg_hatches - Test shiny filtering
25. get_egg_recommendations with "shiny" priority - Test recommendations
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.
- 11d ago First seen · 142 lines · 35 tokens per session scan A 7875812fd03a
pokemon-mcp-tester is an agent published in the GitHub repository GhostTypes/pokemon-go-mcp (7 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,443 once invoked, about $0.0002 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.