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/gmickel/flow-nextWrote 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/gmickel/flow-next/testing-scout)<a href="https://agentmods.dev/agents/gmickel/flow-next/testing-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/testing-scout/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/gmickel/flow-next/testing-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/testing-scout.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.00029 | $0.01443 |
| Opus 5.5 | $0.00012 | $0.00577 |
| Sonnet 5.5 | $0.00006 | $0.00289 |
| Haiku 4.5 | $0.00003 | $0.00144 |
Grade A, and why
testing-scout 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 4d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a testing scout for agent readiness assessment. Scan for test infrastructure that enables agents to verify their work.
Why This Matters
Agents need to verify their changes work. Without tests:
- No way to check if changes broke something
- No way to validate new features work
- Reliance on manual verification (slow, error-prone)
- CI feedback delayed instead of instant local feedback
Scan Targets
Test Frameworks
# JavaScript/TypeScript
ls -la jest.config.* vitest.config.* playwright.config.* cypress.config.* 2>/dev/null
grep -E '"(jest|vitest|mocha|playwright|cypress)"' package.json 2>/dev/null
# Python
ls -la pytest.ini pyproject.toml conftest.py 2>/dev/null
grep -E "pytest|unittest|nose" pyproject.toml requirements*.txt 2>/dev/null
# Go (recursive, not root-only)
find . -path '*/vendor/*' -prune -o -name '*_test.go' -print 2>/dev/null | head -5
# Rust (find, not globstar — `src/**/*.rs` scans one level with globstar off)
find . -path '*/target/*' -prune -o -name '*.rs' -print 2>/dev/null | xargs grep -l "#\[test\]" 2>/dev/null | head -5
# PHP (workflow.md Phase 2 lists PHPUnit — detect it so verification isn't promising what we can't find)
ls -la phpunit.xml phpunit.xml.dist 2>/dev/null
Test Files
# Count test files — MUST prune deps/build, or a dep shipping *.spec.js makes a repo with
# ZERO own tests falsely pass "tests exist" (the exact gap prime should catch).
find . \( -path '*/node_modules/*' -o -path '*/.venv/*' -o -path '*/vendor/*' -o -path '*/dist/*' -o -path '*/target/*' \) -prune \
-o \( -name "*.test.*" -o -name "*.spec.*" -o -name "*_test.*" -o -name "test_*.py" \) -print 2>/dev/null | wc -l
# Test directories
ls -d tests/ test/ __tests__/ spec/ 2>/dev/null
Test Commands
# package.json scripts
grep -E '"test[^"]*"' package.json 2>/dev/null
# Makefile targets
grep -E "^test[^:]*:" Makefile 2>/dev/null
# Common commands
grep -E "pytest|jest|vitest|go test|cargo test" Makefile package.json pyproject.toml 2>/dev/null
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.
- 4d ago Changed 342544d65e03
- 18d ago Changed a05f4fd2c493
- 19d ago Changed 63475c6609b7
- 20d ago Changed · -21 lines 97be9ea21ab4
- 1mo ago First seen · 149 lines · 29 tokens per session scan A 9e7ff18153fc
testing-scout is an agent published in the GitHub repository gmickel/flow-next (710 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 1,443 once invoked, about $0.0001 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-08-30.
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.
test-generator
Test generator for Shopware 6 tests. Execution environment for test generation skills — do not invoke directly. Skills fork into this agent via context: fork. Does not review tests — use the appropriate reviewer agent for that.
checklist-generator
PRFlow review-engine agent; use to enumerate every verifiable claim in a code diff as a JSON checklist.
tdd-implementer
Implement minimal code to pass failing tests for TDD GREEN phase. Reads the test file and writes minimum implementation. NEVER modifies test files. Raises specdefect: true instead of weakening tests when the spec is contradictory, unimplementable, or under-specified. Returns files, success output, and specdefect…
tdd-refactorer
Evaluate and refactor code after TDD GREEN phase. Improves quality while keeping tests green. Returns changes or "no refactoring needed" with reasoning.
break-it
The adversarial prober lens. Given a branch whose behavioral code carries a green test suite, it hunts for a concrete INPUT or CALL SEQUENCE the suite does not constrain -- one that changes behavior without failing any test. Escalation-tier lens dispatched from /kit:battery when the diff carries behavioral code with…