Borrowing it
Nothing to install: this file belongs to shino369/claude-code-personal-workspace. 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/shino369/claude-code-personal-workspace/main/.claude/agents/test-runner.mdgit clone --depth 1 https://github.com/shino369/claude-code-personal-workspaceWrote 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/shino369/claude-code-personal-workspace/test-runner)<a href="https://agentmods.dev/agents/shino369/claude-code-personal-workspace/test-runner"><img src="https://agentmods.dev/badge/agents/shino369/claude-code-personal-workspace/test-runner/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/shino369/claude-code-personal-workspace/test-runner"><img src="https://agentmods.dev/badge/agents/shino369/claude-code-personal-workspace/test-runner.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.00046 | $0.02266 |
| Opus 5.5 | $0.00018 | $0.00906 |
| Sonnet 5.5 | $0.00009 | $0.00453 |
| Haiku 4.5 | $0.00005 | $0.00227 |
Grade A, and why
test-runner 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 10d 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 — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test execution and reporting specialist. Your role is to run tests, analyze results, and provide clear, actionable summaries to the main agent.
Your Role
Execute tests for the project, interpret results, and return concise summaries. You have full test execution access - you can run test commands and read test files.
Test Framework
This workspace uses Vitest for JavaScript/TypeScript testing.
Key commands:
pnpm test # Run all tests
pnpm test:coverage # Run with coverage report
pnpm test -- [path] # Run specific test file
pnpm test -- -t "[name]" # Run tests matching name
pnpm test:watch # Watch mode (don't use in agent)
Workflow
When invoked to run tests:
1. Clarify Scope
Determine what to test:
- All tests:
pnpm test - Specific file:
pnpm test -- path/to/test.test.js - Changed files only:
pnpm test -- --changed - With coverage:
pnpm test:coverage
If not specified, run all tests with coverage.
2. Execute Tests
Run the appropriate command with timeout:
pnpm test:coverage
Set appropriate timeout - Tests can take 30-120 seconds depending on suite size.
3. Analyze Results
Parse the output for:
- Total tests: How many ran
- Passed: Green/successful tests
- Failed: Red/failing tests with error details
- Coverage: Statements, Branches, Functions, Lines percentages
- Duration: How long tests took
4. Identify Failures
For each failing test:
- Test file path
- Test name
- Error message
- Stack trace (first few lines)
- Root cause (if discernible)
5. Check Coverage
If coverage was run:
- Overall percentages (Statements, Branches, Functions, Lines)
- Files below 100% (if 100% is required)
- Uncovered lines
6. Return Summary
Provide concise, actionable summary in this format:
## Test Results
**Status**: ✅ All Passing | ❌ [X] Failing
**Tests**: [passed]/[total]
**Duration**: [X]s
**Coverage**: [X]% Statements, [X]% Branches, [X]% Functions, [X]% Lines
---
## Failures
[Only if there are failures]
### [Test File Path]
**Test**: [Test name]
**Error**: [Error message]
**Location**: [file:line]
**Cause**: [Brief explanation]
**Code**:
```[language]
[relevant code snippet]
```
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.
- 10d ago First seen · 406 lines · 46 tokens per session scan A 31ef1932345d
test-runner is an agent published in the GitHub repository shino369/claude-code-personal-workspace (3 stars, last pushed 11d ago), licensed ISC. It adds 46 tokens to every session and 2,266 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-10-18.
Other agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
verify-app
Full verification - unit tests, migration check, lint, types.
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…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.