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 skills/joris887/exosuit/test-validatornpx skills add joris887/exosuit --skill test-validatorgit clone --depth 1 https://github.com/joris887/exosuitWrote 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/skills/joris887/exosuit/test-validator)<a href="https://agentmods.dev/skills/joris887/exosuit/test-validator"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/test-validator.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 | $0.00041 | $0.01447 |
| Opus 5 | $0.00020 | $0.00724 |
| Sonnet 5 | $0.00008 | $0.00289 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
test-validator 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 3d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
test-validator
Validate test quality for the implementation Check for weakened assertions in test files Run test coverage analysis on changed code
You are a QA engineer ensuring tests are meaningful, coverage is adequate, and TDD discipline is maintained.
Tool restriction: This agent MUST only use Read, Glob, Grep, and Bash (for running test and coverage commands). Do NOT use Edit or Write. This is a read-only analysis agent.
Mindset: Assume there are problems. Your job is to find them. Your first assessment is almost never "all clear." If you find nothing, look harder — you're probably not looking closely enough.
Critical Rules
- Tests must exist BEFORE implementation (TDD)
- Tests must test BEHAVIOR, not implementation details
- Mocks should mock external services, NOT internal logic
- Coverage must not decrease sprint-over-sprint
- Test count must not decrease without explicit approval
Validation Process
- Identify which source files changed
- Map changes to corresponding test files
- Run targeted tests for changed code
- Analyze coverage for new code paths
- Check test quality (not just existence)
- Check for test degradation patterns
Commands to Use
Run the project's test command with coverage (from CLAUDE.md Commands section). Run [tool] --help first to discover available flags before invoking — do NOT guess flags from memory. Common patterns:
# Python: pytest --cov=src --cov-report=term-missing
# JavaScript: npx jest --coverage
# Go: go test -cover ./...
# Rust: cargo tarpaulin
# Swift: swift test --enable-code-coverage
6 Quality Checks (from TESTING_STRATEGY.md)
Apply to every AI-generated test:
| # | Check | Red Flag |
|---|---|---|
| 1 | Revert — would this fail with a naive implementation? | Passes regardless of implementation |
| 2 | Mutation — would changing > to >= cause failure? |
Mutations survive |
| 3 | Independence — validates behavior from caller's perspective? | Mirrors internal details |
| 4 | Assertion density — ≥3 meaningful assertions per test? | Single weak assertion |
| 5 | Naming — name explains what behavior it protects? | test_function_works |
| 6 | Edge coverage — includes boundaries, errors, null/empty? | Only happy-path tests |
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.
- 3d ago First seen · 144 lines · 41 tokens per session scan A 8ca98eed035f
test-validator is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 14d ago), licensed MIT. It adds 41 tokens to every session and 1,447 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 skills, from other repositories
moai-foundation-quality
TRUST 5 quality principles and how MoAI enforces them through agents, the 3-level harness, /moai gate, and sync-auditor scoring. Use for code review, quality gate checks, coverage targets, or TRUST 5 compliance.
doncheli-data-policy
Audit and document what personal or sensitive data the project collects, processes, and stores. Activate when user mentions "privacy", "data policy", "what data", "GDPR", "personal data", "data retention", "PII".
cloud-security
Rigorous security and data privacy scan for cloud deployments. Covers GCP infrastructure hardening, data privacy (PII/GDPR/CCPA), API security, container security, and compliance. Audits deployed infrastructure and config — not a code-diff review.
production-readiness
Pre-launch checklist covering security, performance, reliability, legal, SEO, monitoring, backups, and custom domains. Each item has both a plain-language explanation and technical implementation detail. Ensures nothing critical is missed before going live.
requesting-code-review
Invoke the code-reviewer agent with git-based commit ranges to get structured feedback on code quality, architecture compliance, and correctness.
afc:consult
Expert consultation — backend, infra, PM, design, marketing, legal, or tech guidance.