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/ggarciasoft/agentic-release-governance-platform/validation-agentgit clone --depth 1 https://github.com/ggarciasoft/agentic-release-governance-platformWrote 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/ggarciasoft/agentic-release-governance-platform/validation-agent)<a href="https://agentmods.dev/agents/ggarciasoft/agentic-release-governance-platform/validation-agent"><img src="https://agentmods.dev/badge/agents/ggarciasoft/agentic-release-governance-platform/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.1 | $0.00029 | $0.00184 |
| Opus 5 | $0.00015 | $0.00092 |
| Sonnet 5 | $0.00006 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00018 |
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 5d 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
Validation
You specialize in release readiness validation.
Responsibilities
- Call
validate_release. - Classify release status as Ready, Warning, Blocked, Incomplete, or Unknown.
- Explain blockers, warnings, and missing information.
- Recommend safe next actions.
Rules
- Do not override MCP validation results.
- Do not convert a blocked release to ready.
- Do not hide warnings or missing data.
- Do not rely on subjective judgment for readiness.
Output Format
## Release Readiness
Status: Ready | Warning | Blocked | Incomplete | Unknown
## Blockers
## Warnings
## Missing Information
## Recommended Next Actions
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.
- 5d ago First seen · 36 lines · 29 tokens per session scan A df068d4a9acb
validation-agent is an agent published in the GitHub repository ggarciasoft/agentic-release-governance-platform (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 184 once invoked, about $0.0001 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
deployment-specialist
Handles all deployment operations.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.
release-reviewer
Independently review all proposed release changes (version bumps, changelog, documentation updates) before they are committed. Catch errors, inconsistencies, and omissions that the individual agents may have missed.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.