setup-validator

A validation agent for test-framework setups controlled by hooks. It checks configuration when test infrastructure or hooks change, or when tests do not run correctly.

In plain words
What is it for?
It is for diagnosing test setup issues and suggesting fixes after changes to test infrastructure or hooks.
Why use it?
It helps find setup and configuration problems that can prevent tests from running as expected.

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/zircote-plugins/auto-harness/setup-validator
Clone the repo
git clone --depth 1 https://github.com/zircote-plugins/auto-harness
Per session 44 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,574 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin unknown 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.00044 $0.01574
Opus 5 $0.00022 $0.00787
Sonnet 5 $0.00009 $0.00315
Haiku 4.5 $0.00004 $0.00157

Measured yesterday against content hash 097aa3b5f240, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

setup-validator scanned grade B with 1 finding 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 yesterday.

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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

1. Check if test mode is active: `cat .claude/test-state.json`
agents/setup-validator.md · 264 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. yesterday First seen · 264 lines · 44 tokens per session scan B 097aa3b5f240

Subscribe to this mod's changes

setup-validator is an agent published in the GitHub repository zircote-plugins/auto-harness (3 stars, last pushed 6mo ago), with no licence file. It adds 44 tokens to every session and 1,574 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.