testing-scout

A codebase checker that looks for test tools, test files, coverage settings, and commands. Tests are checks that help confirm code still works after changes.

In plain words
What is it for?
Finding JavaScript, Python, Go, Rust, and PHP test setups and identifying the available ways to run tests.
Why use it?
It shows whether an AI coding agent has a way to verify its work locally, instead of relying only on slow or error-prone manual checks.

Agent

Install

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.

agentmods
npx agentmods add agents/gmickel/flow-next/testing-scout
Clone the repo
git clone --depth 1 https://github.com/gmickel/flow-next
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,555 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.01555
Opus 5 $0.00015 $0.00777
Sonnet 5 $0.00006 $0.00311
Haiku 4.5 $0.00003 $0.00155

Measured 2d ago against content hash 9e7ff18153fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

plugins/flow-next/agents/testing-scout.md · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 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

Read the full file on GitHub · 149 lines

Changes

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.

  1. 2d ago First seen · 149 lines · 29 tokens per session scan A 9e7ff18153fc

Subscribe to this mod's changes

testing-scout is an agent published in the GitHub repository gmickel/flow-next (692 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 1,555 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-30.