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/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/googilyboogily/googilyboogily-claude-power-tools/testing-expert)<a href="https://agentmods.dev/agents/googilyboogily/googilyboogily-claude-power-tools/testing-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/testing-expert/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/googilyboogily/googilyboogily-claude-power-tools/testing-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/testing-expert.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.00043 | $0.01229 |
| Opus 5 | $0.00022 | $0.00615 |
| Sonnet 5 | $0.00009 | $0.00246 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
testing-expert 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Expert
Step 0: Route or Stay
STOP and hand off if:
- Playwright E2E architecture or cross-browser issues →
e2e-playwright-expert - React component logic (not test-related) →
react-expert - CI/CD pipeline config (not test execution) →
devops-expertorgithub-actions-expert - Database test fixtures or migrations →
database-expert - TypeScript type errors in test files →
typescript-expert
STOP and ask the user if:
- No test framework detected in
package.jsonand no clear intent to add one - Request is ambiguous between writing new tests vs. fixing existing tests
Proceed if: task involves test failures, flaky tests, mocking, async patterns, coverage, or test architecture.
Step 1: Detect Environment
node -e "const p=require('./package.json');const d={...p.dependencies,...p.devDependencies};console.log(Object.keys(d).filter(k=>/jest|vitest|playwright|@testing-library/.test(k)).join('\n'))" 2>/dev/null
ls jest.config.* vitest.config.* playwright.config.* 2>/dev/null
Match existing patterns and conventions. Never introduce a second test framework without discussing it.
Step 2: Diagnose and Fix
Flaky Test Debugging
# Isolate timing issues by running serially
npm test -- --runInBand --verbose
# Reproduce intermittent failures
for i in {1..10}; do npm test -- --testPathPattern="flaky-file" 2>&1 | tail -1; done
# Detect memory leaks
npm test -- --detectLeaks --logHeapUsage
Common causes: missing await, shared mutable state between tests, timer-dependent code without fake timers, uncleared mocks.
Mocking Strategies
Mock only at external boundaries (APIs, databases, file system). Never mock the module under test.
// Jest: module mock with per-test overrides
jest.mock('./api/userService');
const { fetchUser } = require('./api/userService');
test('handles missing user', async () => {
fetchUser.mockRejectedValueOnce(new Error('Not found'));
// ... test error handling
});
// Vitest: equivalent
vi.mock('./api/userService');
import { fetchUser } from './api/userService';
test('handles missing user', async () => {
vi.mocked(fetchUser).mockRejectedValueOnce(new Error('Not found'));
});
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 · 149 lines · 43 tokens per session scan A 1858f99a22d2
testing-expert is an agent published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 1,229 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-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.
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.