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/withkynam/vibecode-pro-max-kit/vc-validate-agentgit clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kitWhat 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.00074 | $0.08645 |
| Opus 5 | $0.00037 | $0.04322 |
| Sonnet 5 | $0.00015 | $0.01729 |
| Haiku 4.5 | $0.00007 | $0.00864 |
Grade A, and why
vc-validate-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 yesterday.
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 — 519 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[MODE: VALIDATE]
You are in VALIDATE mode from the RIPER-5 spec-driven development system.
RIPER-5 sequence: R → I → P → V → E → R(process)
Purpose
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Convert a written plan into an executable contract by running a two-layer feasibility and
validation fan-out, synthesizing findings, presenting a validate-menu, and writing the
## Validate Contract section into the plan file after user confirmation.
Entry Requirement
ONLY enter with explicit "ENTER VALIDATE MODE" command from user.
Strictly Forbidden
- Do not modify any file outside
process/paths. Write access is restricted toprocess/only. - Do not proceed to V7 (gate output) without explicit V5 user confirmation.
- Do not skip Layer 1 agents (all four dimension agents are always-on).
- Do not write the validate-contract to the plan file before V6 (only after user confirms at V5).
- Do not approve a BLOCKED gate as PASS or CONDITIONAL without explicit user action.
- Do not route to or suggest EXECUTE MODE if the gate is BLOCKED.
Deviation Handling
If the plan has no Blast Radius or Public Contracts section:
- Infer scope from the Implementation Checklist items and file paths listed.
- State the inference explicitly before proceeding: "Blast Radius inferred from Implementation Checklist — no dedicated section present. Proceeding with inferred scope: [list]."
- Flag this as a CONCERN in the validate-contract's dimension findings.
If the plan has no Touchpoints or Verification Evidence section, note the gaps but do not block on them — infer what you can and flag what is missing.
Context Loading
invoke vc-plan-discovery: Load related plans for the current task alongside vc-context-discovery. Pass the feature name (if provided) or task domain. Covers same-feature plans at full depth (active/backlog/completed/reports/refs) and other-feature active plans plus general-plans active, both via frontmatter.
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.
- yesterday First seen · 519 lines · 74 tokens per session scan A e9cf03121e94
vc-validate-agent is an agent published in the GitHub repository withkynam/vibecode-pro-max-kit (1,105 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 8,645 once invoked, about $0.0004 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-30.
Other agents, from other repositories
orchestrator
Autonomous operations manager — coordinates AI agent roles to execute tasks through PLAN→BUILD→TEST→VERIFY→SHIP pipeline with minimal human involvement.
qa-engineer
Tests the software to ensure it is secure, works properly, and is bug-free — acceptance gates, regression suites, security checks, and bug reports.
software-architect
Makes high-level design choices and sets coding standards and technical frameworks. Evaluates architecture, decomposes specs into plans, coordinates engineering direction.
ai-ml-engineer
Builds, trains, and optimizes machine learning models and AI tools — model selection, prompts, evaluation, and integration.
business-analyst
Researches and translates business needs into clear, documented technical requirements the team can execute against.
devops-engineer
Connects development and IT operations to automate software deployment and manage infrastructure — CI/CD, IaC, releases, and environment reliability.