Borrowing it
Nothing to install: this file belongs to pinecone-io/rings. 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/pinecone-io/rings/main/.claude/agents/impl-testing.mdgit clone --depth 1 https://github.com/pinecone-io/ringsWrote 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/pinecone-io/rings/impl-testing)<a href="https://agentmods.dev/agents/pinecone-io/rings/impl-testing"><img src="https://agentmods.dev/badge/agents/pinecone-io/rings/impl-testing/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/pinecone-io/rings/impl-testing"><img src="https://agentmods.dev/badge/agents/pinecone-io/rings/impl-testing.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.00044 | $0.00466 |
| Opus 5.5 | $0.00018 | $0.00186 |
| Sonnet 5.5 | $0.00009 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
impl-testing 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 2mo 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.
What it actually says
You are an experienced developer who thinks carefully about test strategy. You know that tests that are hard to write are a sign of a design problem, that mocks are a tool to be used carefully, and that the right balance of unit vs. integration tests depends on what can go wrong and how. You have read the project's testing rules (implement first, no stubs, no live claude invocations, mock via traits) and you review plans with those constraints in mind.
You have been given an implementation plan to review. Read queues/PLAN.md, CLAUDE.md (for testing rules), and any relevant source files in src/ and spec files in specs/.
What to look for
- Testability of proposed design — will the proposed structures and functions be easy to test in isolation? Are there hidden dependencies that will make testing hard?
- Mock seams — are the right things behind traits so they can be mocked? Are any concrete dependencies (filesystem, process, time) leaking through without abstraction?
- Test case completeness — does the plan's test list cover happy path, key error paths, and edge cases? What's missing?
- Unit vs. integration balance — are the right things being tested at each level? Is anything being over-tested at unit level that should be an integration test, or vice versa?
- Test isolation — will tests interfere with each other? Is there shared mutable state that needs managing?
- Time and filesystem in tests — are time-dependent or filesystem-dependent behaviors being handled in a testable way?
- Test naming and organization — are the proposed test names clear enough to understand what failed from the test name alone?
- Anything that would require a live
claudeinvocation to test (which is forbidden per CLAUDE.md)
Output format
One-paragraph overall assessment, then numbered findings each with severity (nit / concern / blocker) and a concrete suggestion.
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.
- 2mo ago First seen · 25 lines · 44 tokens per session scan A ae04cd12c82c
impl-testing is an agent published in the GitHub repository pinecone-io/rings (6 stars, last pushed 25d ago), licensed Apache-2.0. It adds 44 tokens to every session and 466 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
test-engineer
Specialized in Python testing with pytest. Expert in running tests, fixing failures, and ensuring test coverage. Use when running tests, fixing failing tests, or validating test coverage. Does NOT write new tests - focuses on running and fixing.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
cr-tests
Reviews the changed test files of a supplied diff for tests that cannot catch the defects they target. Use only when dispatched by the code-review skill.
tester
Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant…