vibecode-pro-max-kit is a set of instructions, agents, skills, hooks, and settings that gives AI coding agents a plan-first software development workflow. It is designed for developers, product owners, and other builders using agents such as Claude Code, Codex, Cursor, Windsurf, or Copilot across different technology stacks. The catalogue entries are the kit's own workflow components.
Borrowing it
Nothing to install: this file belongs to withkynam/vibecode-pro-max-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/withkynam/vibecode-pro-max-kit/main/.claude/agents/vc-validate-agent.mdgit clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kitWrote 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/withkynam/vibecode-pro-max-kit/vc-validate-agent)<a href="https://agentmods.dev/agents/withkynam/vibecode-pro-max-kit/vc-validate-agent"><img src="https://agentmods.dev/badge/agents/withkynam/vibecode-pro-max-kit/vc-validate-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/withkynam/vibecode-pro-max-kit/vc-validate-agent"><img src="https://agentmods.dev/badge/agents/withkynam/vibecode-pro-max-kit/vc-validate-agent.svg" alt="Reviewed on agentmods" width="80" 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.00074 | $0.08645 |
| Opus 5.5 | $0.00030 | $0.03458 |
| Sonnet 5.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 1mo 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 — 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.
- 1mo ago 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,155 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 8,645 once invoked, about $0.0003 per session on Opus 5.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
walkthrough-analyzer
Use this agent after cycle completion for cycles with UI stories, or when the user requests interactive usability testing. Acts like a real first-time user - clicks every button, checks every state transition, and reports what doesn't feel right. Browser-only - never reads source code. Context: Cycle with UI stories…
qa-analyzer
Use this agent after cycle completion or when the user requests bug hunting and QA analysis. World-class QA analyst that finds bugs before users do — thinks like a confused user, power user, and malicious attacker. Documents each issue precisely so it can be filed as a bug. Context: User just completed a cycle and…
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
reviewer
Owns an MCP Task Orchestrator work item's review phase — independently verifies the implementation against its plan and fills the review-phase notes its resolved schema requires.
test-author
Writes tests for a work item independently of its implementation — blind to production source by capability boundary, not by request.
mb-debugger
Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.