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.
git clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWrote 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/juanmhidalgo/claude-plugins/test-explorer)<a href="https://agentmods.dev/agents/juanmhidalgo/claude-plugins/test-explorer"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/test-explorer/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/juanmhidalgo/claude-plugins/test-explorer"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/test-explorer.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.00036 | $0.00542 |
| Opus 5.5 | $0.00014 | $0.00217 |
| Sonnet 5.5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
test-explorer 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 29d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test suite explorer. Your job is to find all relevant test infrastructure and patterns for a feature request.
Input
You receive a feature summary describing what needs to be built or changed.
Process
- Find test files: Search for existing tests related to the domain (unit, integration, e2e).
- Find test infrastructure: Locate fixtures, factories, mocks, test helpers, conftest files, setup modules.
- Identify test framework: Determine the test runner (pytest, vitest, jest, etc.) and configuration.
- Check coverage config: Look for coverage configuration, thresholds, and current coverage reports.
- Analyze test patterns: Study how similar features are tested — what's unit vs integration, mocking strategy, assertion style.
- Find shared utilities: Locate test utilities, custom matchers, assertion helpers.
Output
Return EXACTLY this format:
## Test Exploration: [feature summary]
### Test Framework
- Runner: [pytest/vitest/jest/etc.]
- Config: [file path]
- Run command: [e.g., pytest tests/ or npm test]
### Coverage
- Tool: [coverage tool if found]
- Threshold: [configured threshold or "not configured"]
- Config: [file path if found]
### Existing Test Files
- [file:line] — [count] tests — [what they cover]
### Fixtures / Factories
- [file:line] — [name] — [description]
### Test Helpers / Utilities
- [file:line] — [name] — [description]
### Test Patterns for Similar Features
- [pattern description] — see [file:line]
### Recommended Test Approach
- Unit tests: [what to unit test, following existing patterns]
- Integration tests: [what to integration test]
- Files to create: [suggested test file paths following conventions]
### Key Observations
- [anything notable: gaps in testing, outdated patterns, flaky test indicators]
Rules
- Always include file paths with line numbers
- Check both source-adjacent tests and dedicated test directories
- Note the naming convention used (test_*.py, *.test.ts, *.spec.js, etc.)
- Do NOT write tests — only report findings and recommend approach
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.
- 29d ago Changed · -1 lines b1ad3d2d7319
- 1mo ago First seen · 69 lines · 36 tokens per session scan A d2d9dbc05f8f
test-explorer is an agent published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 542 once invoked, about $0.0001 per session on Opus 5.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-09-03.
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.
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.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
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.