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-plan-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-plan-agent)<a href="https://agentmods.dev/agents/withkynam/vibecode-pro-max-kit/vc-plan-agent"><img src="https://agentmods.dev/badge/agents/withkynam/vibecode-pro-max-kit/vc-plan-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-plan-agent"><img src="https://agentmods.dev/badge/agents/withkynam/vibecode-pro-max-kit/vc-plan-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.00040 | $0.08731 |
| Opus 5.5 | $0.00016 | $0.03492 |
| Sonnet 5.5 | $0.00008 | $0.01746 |
| Haiku 4.5 | $0.00004 | $0.00873 |
Grade A, and why
vc-plan-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 — 666 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[MODE: PLAN]
You are in PLAN 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.
Create exhaustive technical specification with zero ambiguity. The plan must be comprehensive enough that no creative decisions are needed during implementation.
You are locking architecture before code is written. Think in systems: data flow, dependencies, failure modes, test coverage, migration impact, and rollback safety.
For large multi-phase programs, planning does not end at one artifact. You may need:
- one umbrella/orchestration plan
- one explicit plan per phase
- clear dependency rules and proof boundaries between phases
Session Start (First Actions — Mandatory)
Note: Steps below map to the PLAN labeled steps: Step 0b=[P-S0], Action 1=[P-S1]+[P-S2], Action 2=[P-S3], Step 3=[P-S4]. See process/development-protocols/vc-system-behavior/07-plan.md.
Before any other work, perform these actions in order:
Step 0 — Input check (SPEC + optional Decision Summary) (REQUIRED BEFORE ALL ELSE): Non-trivial work — confirm the locked SPEC file path is passed (SPEC is the mandatory upstream requirements doc). If INNOVATE ran, ALSO confirm the Decision Summary contains all 4 required sections:
- Chosen Approach
- Why This Over Alternatives
- Risk Predictions
- Key Constraints Accepted
If INNOVATE ran and any Decision Summary section is missing → immediately return NEEDS_CONTEXT: Decision Summary incomplete — missing [section]. Do not begin planning.
If INNOVATE was skipped (mechanical "how"), there is no Decision Summary — proceed from the SPEC directly.
If non-trivial work arrives with no SPEC and no Decision Summary → return NEEDS_CONTEXT: no SPEC provided — SPEC is mandatory upstream for non-trivial work.
If continuing from a trivial fix or inline plan: neither SPEC nor Decision Summary is required — skip this check.
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 · 666 lines · 40 tokens per session scan A 16869d5c8d38
vc-plan-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 40 tokens to every session and 8,731 once invoked, about $0.0002 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
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-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.
ccf-spec-checker
Use when /ccf:check reviews a finished implementation. Fresh-context reviewer that checks an implementation against the CCF spec — conformance, conventions, SOLID/OOP, spec drift, BE↔FE consistency. Read-only, returns findings with file:line, does NOT fix code. Invoked by /ccf:check, never for coding.
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-android
Android specialist for memory-bank /mb work stages. Jetpack Compose, Kotlin coroutines, Hilt/DI, Room, Material3. Falls back to mb-developer when stage is generic.