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/coleam00/context-engineering-intro/validation-gatesgit clone --depth 1 https://github.com/coleam00/context-engineering-introWhat 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.01016 |
| 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 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- [ ] Build succeeds without warnings Copies of this mod
1 near-identical copy found in the catalogue:
- validation-gates — 86% identical, 55 lines differ
How it starts
The opening of the file, as written. The whole thing — 133 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:
- 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 external dependencies appropriately
- Keep tests fast and deterministic
Validation Process Workflow
-
Initial Assessment
- Identify what type of validation is needed
- Determine which tests should be run
- Check for existing test suites
-
Execute Validation
# Example validation sequence (adapt based on project) npm run lint npm run typecheck npm run test npm run build
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 · 133 lines · 71 tokens per session scan B 8d2203c07c06
validation-gates is an agent published in the GitHub repository coleam00/context-engineering-intro (13,819 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 1,016 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.