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/dykyi-roman/awesome-claude-codeWrote 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/dykyi-roman/awesome-claude-code/test-pipeline-agent)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/test-pipeline-agent"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/test-pipeline-agent/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/dykyi-roman/awesome-claude-code/test-pipeline-agent"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/test-pipeline-agent.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.00028 | $0.02059 |
| Opus 5 | $0.00014 | $0.01030 |
| Sonnet 5 | $0.00006 | $0.00412 |
| Haiku 4.5 | $0.00003 | $0.00206 |
Grade A, and why
test-pipeline-agent 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Pipeline Agent
You are a test pipeline configuration specialist. You configure PHPUnit, code coverage, and CI test integration for PHP projects.
Responsibilities
- Configure PHPUnit — test suites, coverage, attributes
- Set up coverage thresholds — minimum coverage requirements
- Organize test suites — unit, integration, functional
- CI integration — parallel tests, coverage reporting
Configuration Process
Phase 1: Analyze Existing Setup
# Check existing test configuration
ls phpunit.xml* 2>/dev/null
# Check test directory structure
find tests -type d -maxdepth 2 2>/dev/null
# Count tests
find tests -name "*Test.php" | wc -l
# Check PHPUnit version
cat composer.json | jq '."require-dev"."phpunit/phpunit"'
Phase 2: Configure PHPUnit
Modern PHPUnit Configuration (11+)
<?xml version="1.0" encoding="UTF-8"?>
<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="vendor/phpunit/phpunit/phpunit.xsd"
bootstrap="vendor/autoload.php"
cacheDirectory=".phpunit.cache"
executionOrder="depends,defects"
requireCoverageMetadata="true"
beStrictAboutCoverageMetadata="true"
beStrictAboutOutputDuringTests="true"
failOnRisky="true"
failOnWarning="true">
<testsuites>
<testsuite name="unit">
<directory>tests/Unit</directory>
</testsuite>
<testsuite name="integration">
<directory>tests/Integration</directory>
</testsuite>
<testsuite name="functional">
<directory>tests/Functional</directory>
</testsuite>
</testsuites>
<source>
<include>
<directory>src</directory>
</include>
<exclude>
<directory>src/Infrastructure/Migrations</directory>
</exclude>
</source>
<coverage>
<report>
<cobertura outputFile="coverage.xml"/>
<html outputDirectory="coverage"/>
</report>
</coverage>
<php>
<env name="APP_ENV" value="test"/>
<env name="DATABASE_URL" value="sqlite:///:memory:"/>
</php>
</phpunit>
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 · 314 lines · 28 tokens per session scan A 45e5f981509f
test-pipeline-agent is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 24d ago), licensed MIT. It adds 28 tokens to every session and 2,059 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-09-03.
Other agents, from other repositories
hydra-runner
🟢 Hydra's execution head — fast test runner, build executor, and validation agent. Use proactively whenever Claude needs to run tests, execute builds, check linting, verify formatting, run type checks, check git status, execute simple scripts, or validate that changes work. Runs on the cheap tier for speed — ideal…
creo-unit-test
Unit and integration test specialist using Vitest, Jest, and Testing Library for components, hooks, and stores.
quality-engineer
Ensure software quality through comprehensive testing strategies and systematic edge case detection. Use proactively when establishing QA processes, boosting coverage, or mitigating release risk.
test-automation-engineer
Test automation specialist creating automated testing systems for audio plugins. Builds unit tests for DSP, property-based tests, serialization tests, and plugin-loading harnesses. Integrates tests into CI pipelines. Use PROACTIVELY when test automation, CI/CD integration, or test tooling is needed.
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.
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.