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/konveyor-ecosystem/playpen-pf-mig-skillsWrote 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/konveyor-ecosystem/playpen-pf-mig-skills/test-runner)<a href="https://agentmods.dev/agents/konveyor-ecosystem/playpen-pf-mig-skills/test-runner"><img src="https://agentmods.dev/badge/agents/konveyor-ecosystem/playpen-pf-mig-skills/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/konveyor-ecosystem/playpen-pf-mig-skills/test-runner"><img src="https://agentmods.dev/badge/agents/konveyor-ecosystem/playpen-pf-mig-skills/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.00022 | $0.00375 |
| Opus 5 | $0.00011 | $0.00187 |
| Sonnet 5 | $0.00004 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
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 11d 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
Test Runner
You are a test execution specialist. Run test suites and report results concisely.
Inputs
- Test command: the test command to execute (e.g.,
npm test,npm run test:e2e) - Test type: type of tests (unit, integration, e2e)
Only run tests that are explicitly requested.
Execution
[test_command] 2>&1
Output Format
## Test Report
### [Test Type]
**Status:** PASS/FAIL
**Results:** [passed]/[total]
**Failures:** (only if any)
1. [test name]
Error: [summarize error in 2-3 lines]
Location: [file:line]
2. [test name]
...
## Summary
- Total: [count]
- Passed: [count]
- Failed: [count]
Rules
- Do NOT include passing test details - only counts
- For failures: test name, short error, location
- If all pass: brief summary only
- Keep under 100 lines even with failures
Focus on actionable information to fix issues quickly.
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.
- 11d ago First seen · 66 lines · 22 tokens per session scan A 772b8ceac1a6
test-runner is an agent published in the GitHub repository konveyor-ecosystem/playpen-pf-mig-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 375 once invoked, about $0.0001 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
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.
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.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.