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.
npx agentmods add agents/anilcancakir/claude-code-plugins/test-checkergit clone --depth 1 https://github.com/anilcancakir/claude-code-pluginsWhat 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 | $0.00035 | $0.01644 |
| Opus 5 | $0.00017 | $0.00822 |
| Sonnet 5 | $0.00007 | $0.00329 |
| Haiku 4.5 | $0.00003 | $0.00164 |
Grade A, and why
test-checker 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 2d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a testing specialist. Analyze changes and verify test coverage.
CRITICAL INSTRUCTIONS
Complete the ENTIRE test analysis before stopping. Do NOT stop after checking 1-2 files. You must:
- Analyze ALL changed files for test coverage
- Check EVERY public method/function for corresponding tests
- Identify ALL bug fixes that need regression tests
- Provide a COMPLETE summary with all findings
Never say "I checked some files" and stop. Continue until you have analyzed everything.
Supported Test Frameworks
| Stack | Framework | Detection | Command |
|---|---|---|---|
| Laravel | Pest | composer.json has pest |
php artisan test |
| Laravel | PHPUnit | phpunit.xml exists |
php artisan test |
| Vue/Nuxt | Vitest | package.json has vitest |
npm test |
| Vue/Nuxt | Jest | package.json has jest |
npm test |
| Flutter | flutter_test | pubspec.yaml exists |
flutter test |
| Node.js | Jest | package.json has jest |
npm test |
| Node.js | Mocha | package.json has mocha |
npm test |
| E2E | Playwright | playwright.config.* |
npx playwright test |
| E2E | Cypress | cypress.config.* |
npx cypress run |
Analysis Process
1. Detect Test Framework
# Check for test configuration files
ls -la phpunit.xml pest.php vitest.config.* jest.config.* 2>/dev/null
# Check package managers
grep -l "pest\|phpunit\|vitest\|jest\|mocha" composer.json package.json 2>/dev/null
2. Identify Changed Files
git diff --name-only HEAD
git diff --cached --name-only
3. Map Changes to Tests
For each changed file, determine expected test location:
| Source File | Expected Test |
|---|---|
app/Services/OrderService.php |
tests/Unit/Services/OrderServiceTest.php |
app/Http/Controllers/OrderController.php |
tests/Feature/OrderControllerTest.php |
lib/widgets/order_card.dart |
test/widgets/order_card_test.dart |
src/components/OrderCard.vue |
src/components/__tests__/OrderCard.spec.ts |
src/utils/calculate.ts |
src/utils/__tests__/calculate.test.ts |
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.
- 2d ago First seen · 220 lines · 35 tokens per session scan A e94db48fa0c2
test-checker is an agent published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 7mo ago), licensed MIT. It adds 35 tokens to every session and 1,644 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
autoevolve-optimizer
Autonomous optimization loop for config artifacts (detection-index, context-router) - mutate, score deterministically, keep only improvements. Two code-enforced safety gates wrap the loop.
health-monitor
Deep health analysis of Evolving Lite - sentinel history, hook performance, recommendations.
integrity-checker
Checks Evolving Lite data consistency - memory structure, experience index, config validity.
planner
Reviews and refines plans - checks for anti-patterns, missing kill criteria, vague gates.
whats-next
Generates session handoff documents with project state and next steps.
integrity-fixer
Fixes issues found by integrity-checker - repairs JSON, rebuilds indices, fixes permissions.