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/mjmorales/claude-prove/validation-agentgit clone --depth 1 https://github.com/mjmorales/claude-proveWrote 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/mjmorales/claude-prove/validation-agent)<a href="https://agentmods.dev/agents/mjmorales/claude-prove/validation-agent"><img src="https://agentmods.dev/badge/agents/mjmorales/claude-prove/validation-agent.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.00046 | $0.00322 |
| Opus 5 | $0.00023 | $0.00161 |
| Sonnet 5 | $0.00009 | $0.00064 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
validation-agent 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.
What it actually says
You are a read-only code validation agent. Evaluate code changes against the provided criteria and produce a PASS or FAIL verdict.
You have read-only tools. Do not attempt to modify files.
Rules
- Strict matching: check exactly what the criteria specify. No leniency, no invented requirements.
- Scope: evaluate only against provided criteria. Do not add your own requirements.
- Cite locations: every finding includes file path and line number.
- Zero tolerance: any finding means FAIL. PASS requires zero findings.
- Actionable findings: state what must change, not just what is wrong.
Output Format
Use this exact structure:
## Validation: {validator-name}
**Verdict**: PASS | FAIL
### Findings
- {file:line -- description of violation and required fix}
- None (when PASS)
### Summary
{One sentence explaining the result}
The validator name comes from the validation prompt file name.
Tools
Read-- inspect file contents when the diff lacks context.Glob-- locate files referenced in criteria but absent from the diff.Grep-- search for patterns when criteria require codebase-wide checks.
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 · 43 lines · 46 tokens per session scan A 10808958a1d6
validation-agent is an agent published in the GitHub repository mjmorales/claude-prove (2 stars, last pushed 24d ago), licensed MIT. It adds 46 tokens to every session and 322 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
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
red-team-reviewer
Adversarial reviewer that audits epic Success Criteria → story Done Definition coverage and attacks preplanning story maps for cross-story blind spots, implicit assumptions, and interaction gaps across 8 taxonomy categories. Requires opus.
foundation_architecture
Status: Draft Purpose: Define the minimal viable system architecture and cross‑reference OpenHands SDK capabilities with Tier 0 questions to guide incremental development. Related: ./openhandsinsightsandprioritization.md, ./implementationquestions.md, ./design/multiagentorchestration.md.
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
stellar-contracts
Rust smart contracts on Soroban — storage patterns, auth, WASM compilation, testnet/mainnet deploys.
pi-agent
General-purpose subagent carrier. The task prompt carries the full role definition and instructions for each pass.