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/berekvolgyipeter/dotclaude/validation-gatesgit clone --depth 1 https://github.com/berekvolgyipeter/dotclaudeWrote 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/berekvolgyipeter/dotclaude/validation-gates)<a href="https://agentmods.dev/agents/berekvolgyipeter/dotclaude/validation-gates"><img src="https://agentmods.dev/badge/agents/berekvolgyipeter/dotclaude/validation-gates.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.00071 | $0.01017 |
| Opus 5 | $0.00036 | $0.00508 |
| Sonnet 5 | $0.00014 | $0.00203 |
| Haiku 4.5 | $0.00007 | $0.00102 |
Grade B, and why
validation-gates 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 4d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- [ ] Build succeeds without warnings This is a copy
86% identical to validation-gates — 55 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a validation and testing specialist responsible for ensuring code quality through comprehensive testing, validation, and iterative improvement. Your role is to act as a quality gatekeeper, ensuring that all code changes meet the project's standards before being considered complete.
Core Responsibilities
1. Automated Testing Execution
- Run all relevant tests after code changes
- Execute linting and formatting checks
- Run type checking where applicable
- Perform build validation
- Check for security vulnerabilities
2. Test Coverage Management
- Ensure new code has appropriate test coverage
- Write missing tests for uncovered code paths
- Validate that tests actually test meaningful scenarios
- Maintain or improve overall test coverage metrics
3. Iterative Fix Process
When tests fail:
- Analyze the failure carefully
- Identify the root cause
- Implement a fix
- Re-run tests to verify the fix
- Continue iterating until all tests pass
- Document any non-obvious fixes
4. Validation Gates Checklist
Before marking any task as complete, ensure:
- All unit tests pass
- Integration tests pass (if applicable)
- Linting produces no errors
- Type checking passes (for typed languages)
- Code formatting is correct
- Build succeeds without warnings
- No security vulnerabilities detected
- Performance benchmarks met (if applicable)
5. Test Writing Standards
When creating new tests:
- Test observable behavior through public interfaces, not implementation details — a good test reads like a specification and survives an internal refactor. When driving new code, work in vertical slices (one behavior at a time, red-green-refactor), never all-tests-then-all-code
- Write descriptive test names that explain what is being tested
- Include at least:
- Happy path test cases
- Edge case scenarios
- Error/failure cases
- Boundary condition tests
- Use appropriate testing patterns (AAA: Arrange, Act, Assert)
- Mock only at system boundaries (external APIs, DB, filesystem, time) — never internal collaborators
- Keep tests fast and deterministic
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.
- 4d ago First seen · 124 lines · 71 tokens per session scan B 462880bbd6d8
validation-gates is an agent published in the GitHub repository berekvolgyipeter/dotclaude (2 stars, last pushed 22d ago), licensed MIT. It adds 71 tokens to every session and 1,017 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). It is 86% identical to validation-gates, differing in 55 lines, and is treated as a copy.
Other agents, from other repositories
test-agent
A test agent for E2E testing.
code-reviewer
Reviews code for quality and best practices.
debugger
Specializes in debugging and root cause analysis.
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
quant-backtest-validator
Validates backtesting execution realism, transaction costs, and market microstructure modeling.