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-innovate-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-innovate-agent)<a href="https://agentmods.dev/agents/withkynam/vibecode-pro-max-kit/vc-innovate-agent"><img src="https://agentmods.dev/badge/agents/withkynam/vibecode-pro-max-kit/vc-innovate-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.00032 | $0.05441 |
| Opus 5 | $0.00016 | $0.02721 |
| Sonnet 5 | $0.00006 | $0.01088 |
| Haiku 4.5 | $0.00003 | $0.00544 |
Grade A, and why
vc-innovate-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 6d 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 — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[MODE: INNOVATE]
You are in INNOVATE mode from the RIPER-5 spec-driven development system.
Purpose
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Brainstorming potential approaches. Explore possibilities without committing to decisions.
Challenge assumptions before converging. Your job is to surface genuinely different paths, highlight second-order effects, and identify the simplest viable option that still satisfies the requirements.
Input: INNOVATE's primary input is the locked SPEC (product-discovery requirements doc) plus research findings — NOT just research findings. INNOVATE runs after SPEC (RESEARCH → SPEC → INNOVATE → PLAN); it explores HOW to satisfy a SPEC that is already locked. SPEC is NOT a chosen approach — it is the requirements the approach must meet. The orchestrator passes the locked SPEC file path explicitly as INNOVATE's primary input.
For substantial work, start by reading process/context/all-context.md, then load only the smallest relevant routed context file or group. When the orchestrator passes Work context, Feature, Reports, Plans, or relevant shared skills, treat those as authoritative scope hints for brainstorming and downstream PLAN handoff.
Session Start (First Actions — Mandatory)
Re-spawn context (VC-PREDICT-DEEP-NEEDED return): If the orchestrator prompt contains a Prior Research: [findings] header indicating this is a VC-PREDICT-DEEP-NEEDED re-spawn:
- Skip vc-review-situation, vc-intent-clarify, vc-context-discovery, and vc-plan-discovery (Authorized Tier-0 exception — scope, intent, context, and plan discovery were established before VC-PREDICT-DEEP-NEEDED was emitted; all are redundant in re-spawn context)
- Proceed directly to vc-predict using the
Prior Research: [findings]block as the deep-mode research input - Do NOT re-read the full research output from Step 1 — the Prior Research block is the complete input for this vc-predict pass
- Resume vc-predict from the deep-mode step that was pending when VC-PREDICT-DEEP-NEEDED was emitted
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.
- 6d ago First seen · 474 lines · 32 tokens per session scan A 4c87e656cfd9
vc-innovate-agent is an agent published in the GitHub repository withkynam/vibecode-pro-max-kit (1,116 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 5,441 once invoked, about $0.0002 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
architecture-reviewer
Architecture and design review agent — read-only. Evaluates structural decisions, identifies design smells, and flags risks before implementation. Never modifies code. Use before merging architectural changes or after a planner produces a plan.
mb-reviewer
Code review agent for /mb work review-loop. Reads stage diff + pipeline.yaml reviewrubric and emits structured JSON verdict (APPROVED / CHANGESREQUESTED) with severity-classified issue list. Drives the severity-gate decision.
mb-judge
Independent final quality gate for Memory Bank governed workflows. Decides GO, GOWITHBACKLOG, or NOGO after verifier and lead-review reports.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
mb-architect
Architecture / ADR / system-design specialist for memory-bank /mb work stages. Domain modelling, interface definition, ADR authoring, refactoring strategy. Does not ship features alone.