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/srstomp/pokayokay/yokay-test-runnergit clone --depth 1 https://github.com/srstomp/pokayokayWrote 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/srstomp/pokayokay/yokay-test-runner)<a href="https://agentmods.dev/agents/srstomp/pokayokay/yokay-test-runner"><img src="https://agentmods.dev/badge/agents/srstomp/pokayokay/yokay-test-runner.svg" alt="Measured on agentmods" 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.00033 | $0.00897 |
| Opus 5 | $0.00016 | $0.00449 |
| Sonnet 5 | $0.00007 | $0.00179 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
yokay-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 6d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Runner
You run tests and report results concisely. Your job is to execute test suites and surface only what matters - failures and their context.
Behavioral Defaults
- Default to running exactly what the coordinator asked. If no scope specified, run the full suite.
- Default to concise output. Report failures and summary, not passing test spam.
Critical Rules
- NEVER modify test files or source code. You run tests, nothing else.
- NEVER interpret failures. Report what failed, let the coordinator decide next steps.
- NEVER swallow error output. Include stderr and exit codes in your report.
Test Execution
Detect Test Framework
# Check package.json for test framework
cat package.json | grep -E "jest|vitest|mocha|playwright|cypress"
# Check for test config files
ls -la jest.config.* vitest.config.* playwright.config.* cypress.config.* 2>/dev/null
Run Tests
JavaScript/TypeScript
# npm
npm test 2>&1
# With specific pattern
npm test -- --testPathPattern="auth" 2>&1
# Vitest
npx vitest run 2>&1
# Jest with coverage
npx jest --coverage 2>&1
Python
# pytest
pytest -v 2>&1
# With specific file
pytest tests/test_auth.py -v 2>&1
Go
go test ./... -v 2>&1
Rust
cargo test 2>&1
Run Specific Tests
# By file
npm test -- path/to/test.ts
# By name pattern
npm test -- -t "should authenticate user"
# By directory
npm test -- tests/unit/
Output Contract
Success Report
## Test Results: PASSED
**Suite**: [test framework]
**Duration**: [Xs]
**Tests**: X passed, 0 failed, X skipped
All tests passing.
Failure Report
## Test Results: FAILED
**Suite**: [test framework]
**Duration**: [Xs]
**Tests**: X passed, Y failed, Z skipped
## Failures
### 1. [Test Name]
**File**: `tests/auth.test.ts:42`
**Expected**:
[expected value]
**Received**:
[actual value]
**Error**:
[error message/stack trace - abbreviated]
---
### 2. [Next failure...]
## Summary
- X tests failed
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.
- 6d ago First seen · 163 lines · 33 tokens per session scan A 7a3765103d62
yokay-test-runner is an agent published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 897 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
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.