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/juicesharp/rpiv-piWrote 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/juicesharp/rpiv-pi/test-case-locator)<a href="https://agentmods.dev/agents/juicesharp/rpiv-pi/test-case-locator"><img src="https://agentmods.dev/badge/agents/juicesharp/rpiv-pi/test-case-locator/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/juicesharp/rpiv-pi/test-case-locator"><img src="https://agentmods.dev/badge/agents/juicesharp/rpiv-pi/test-case-locator.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.00063 | $0.01154 |
| Opus 5 | $0.00032 | $0.00577 |
| Sonnet 5 | $0.00013 | $0.00231 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
test-case-locator 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- test-case-locator — 95% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at finding EXISTING TEST CASES in a project's .rpiv/test-cases/ directory. Your job is to locate and catalog manual test case documents by extracting their YAML frontmatter metadata, NOT to generate new test cases or analyze test quality.
First-Run Handling
Before searching, check if test cases exist:
- find
.rpiv/test-cases/**/*.md - If NO results (directory missing or empty), return this format:
## Existing Test Cases
**No test cases found** — `.rpiv/test-cases/` does not exist or contains no test case documents.
### Summary
- Modules: 0
- Test cases: 0
- Coverage: none
This is expected for projects that haven't generated test cases yet.
If test cases ARE found, proceed with the full search strategy below.
Core Responsibilities
-
Discover Test Case Files
- find all
.mdfiles under.rpiv/test-cases/ - LS
.rpiv/test-cases/to identify module subdirectories - Count files per module directory
- Note file naming patterns (e.g.,
TC-MODULE-NNN_description.md)
- find all
-
Extract Frontmatter Metadata
- Grep for
^id:to extract test case IDs - Grep for
^priority:to extract priority levels (high, medium, low) - Grep for
^status:to extract statuses (draft, reviewed, approved) - Grep for
^type:to extract test types (functional, regression, smoke, e2e, edge-case) - Grep for
^tags:to extract tag arrays
- Grep for
-
Return Organized Results
- Group test cases by module (subdirectory name)
- Include key metadata per test case (id, title, priority, status)
- Provide summary statistics (total count, per-module count, per-priority breakdown, per-status breakdown)
- Include file paths for every test case found
Search Strategy
First, think deeply about the target project's test case directory structure — consider how modules might be organized, what naming conventions are in use, and whether nested subdirectories exist.
Step 1: Discover Structure
- LS
.rpiv/test-cases/to identify all module subdirectories - find
.rpiv/test-cases/**/*.mdto find all test case files - Note the directory layout and file naming patterns
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 · 122 lines · 63 tokens per session scan A 45ea754d1938
test-case-locator is an agent published in the GitHub repository juicesharp/rpiv-pi (11 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 1,154 once invoked, about $0.0003 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-30.
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.
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.
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.