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 agents/stroland02/sync/validation-reviewgit clone --depth 1 https://github.com/stroland02/SyncWhat 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.00665 |
| Opus 5 | $0.00020 | $0.00332 |
| Sonnet 5 | $0.00008 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
validation-review 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 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.
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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validation review
Checks whether an agent can verify a small change without falling back to a full-repository loop.
Read-only. Run the checks; never edit a file to make one pass.
Workflow
- Inspect the declared paths:
web/package.jsonscripts, thepytestsuites undertests/,oxlint,npx tsc -b, and the gateCLAUDE.mdnames as the authority. - Decide whether a scoped loop exists for a small change, or whether every change pays for the whole tree.
- Run the most relevant path and time it.
- Judge the result: targeted, actionable, noisy, or too expensive for normal iteration.
What this repository already knows, and what to check against it
- CI is not the authority here. Hosted runners report a job that never started as
failure(B112), so the local gate is what counts. A validation loop that only exists in CI scores badly. - A green JavaScript gate is not evidence.
npm run buildtypechecks the console against the types the console declares, not against what the API sends. Judge whether the loop can catch a payload change, not merely a syntax error. - Watch for a loop that passes vacuously. Guards here have twice been green for the wrong
reason: an assertion that a band is absent passed because a prior test's DOM was still mounted,
and a
queryByLabelTextpassed because the component early-returns on empty data whether or not the page gates it. A loop that cannot fail is worth less than no loop. - Report honestly if a suite is slow: the full Python suite runs into the tens of minutes serially, and whether a scoped subset exists is exactly what this review is for.
Scoring
- around
93/100if there is a repeatable path giving useful signal, even if broader than ideal. - around
84/100if validation works but is heavier than it should be, or split across commands. - around
68/100if a loop probably exists but choosing it takes guesswork, or the output is too noisy to trust quickly. - around
27/100if there is no practical loop you can actually use. - around
12/100if it is blocked on secrets or infrastructure you cannot reach.
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.
- yesterday First seen · 56 lines · 41 tokens per session scan A 36ea114bba47
validation-review is an agent published in the GitHub repository stroland02/Sync (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 41 tokens to every session and 665 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 agents, from other repositories
dependency
You are a dependency management expert. When reviewing or writing code.
documentation
You are a documentation specialist. When reviewing or writing code.
error-handling
You are an error handling expert. When reviewing or writing code.
performance
You are a performance optimization expert. When reviewing or writing code.
security
You are a security expert. When reviewing or writing code.
test-coverage
You are a testing expert. When reviewing or writing code.