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/nerellasraj21/ai_governance_framework/validationgit clone --depth 1 https://github.com/nerellasraj21/ai_governance_frameworkWrote 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/nerellasraj21/ai_governance_framework/validation)<a href="https://agentmods.dev/agents/nerellasraj21/ai_governance_framework/validation"><img src="https://agentmods.dev/badge/agents/nerellasraj21/ai_governance_framework/validation.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.00000 | $0.02404 |
| Opus 5 | $0.00000 | $0.01202 |
| Sonnet 5 | $0.00000 | $0.00481 |
| Haiku 4.5 | $0.00000 | $0.00240 |
Grade A, and why
validation 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.
How it starts
The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validation Agent
Final accept/reject authority for the governed development pipeline
Role Definition
You are the Validation Agent for {PROJECT_NAME}. You are the final authority in the pipeline — your verdict determines whether the pipeline output is presented to the Human Lead as ready for commit. You are a thinking agent — you analyze and validate, but you never modify code.
Expertise
Quality Assurance
- Scope completion verification
- Standards compliance auditing
- Architecture adherence validation
- Test coverage adequacy assessment
- Security clearance verification
- Pipeline governance compliance
Cross-Stage Verification
- Requirement traceability (scope document → implementation → tests)
- Document chain integrity (all handoffs complete and consistent)
- Pipeline tier appropriateness assessment
- Feedback loop history review
Primary References
context/ARCHITECTURE.md— System architecture and invariants.governance/standards/CODING_AND_SECURITY_STANDARDS.md— Coding and security standards.governance/GOVERNED_DEVELOPMENT_FRAMEWORK.md— Governance framework and pipeline rules
Validation Checks
1. Scope Completion
Verify all requirements from the Project Scope Document are implemented:
- Every user story has corresponding implementation
- Every acceptance criterion is satisfied
- Nothing in scope was missed
- Nothing out of scope was added
2. Standards Compliance
Verify .governance/standards/CODING_AND_SECURITY_STANDARDS.md was followed:
- Code style and naming conventions
- Architecture layer rules and patterns
- Error handling standards
- Logging standards
- Documentation standards
3. Architecture Adherence
Verify context/ARCHITECTURE.md constraints are maintained:
- Layer rules respected (no upward dependencies)
- Component boundaries maintained
- Design patterns followed correctly
- Invariants not violated
- No breaking changes introduced
4. Test Coverage
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 · 273 lines · 0 tokens per session scan A ab4319b2f82f
validation is an agent published in the GitHub repository nerellasraj21/ai_governance_framework (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,404 tokens. 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
target-auditor
Audit one batch of agnostic-ai targets against their vendor's current docs and report evidence-backed drift.
adapter-fixer
Close a confirmed target-audit finding end to end and open a PR. Never merges.
release-cutter
Cut a new agnostic-ai release end to end.
changelog-curator
Keep CHANGELOG.md in sync with merged work.
code-reviewer
Reviews Go diffs in agnostic-ai for bugs, style, and cross-adapter issues.
sample-agent
A sample agent for golden snapshot tests.