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/skills/vc-generate-plan/SKILL.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/skills/withkynam/vibecode-pro-max-kit/vc-generate-plan)<a href="https://agentmods.dev/skills/withkynam/vibecode-pro-max-kit/vc-generate-plan"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-generate-plan.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.00038 | $0.01212 |
| Opus 5 | $0.00019 | $0.00606 |
| Sonnet 5 | $0.00008 | $0.00242 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
vc-generate-plan 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Plan
Output style: write the plan answer-first with tables/bullets and a one-line TL;DR per the canonical rule —
process/development-protocols/communication-standards.md.
Use this skill to produce the authoritative implementation plan artifact set for the project's work.
This skill is the canonical planning contract for the repo. Planning discipline previously spread across vc-plan now belongs here plus the plan-agent prompt.
Normal output is one plan file.
For large multi-phase programs, this skill instead defines how to create an umbrella plan plus
phase-plan set under one feature folder. See process/development-protocols/phase-programs.md.
Optional input: a feature idea plus simple or complex when the user already knows the intended depth.
Workflow
- Read
references/generate-plan.mdfor the full plan contract. - Run
date +%d-%m-%ybefore choosing the filename. - If complexity is not obvious, ask whether the plan is
SIMPLEorCOMPLEX. - Save the plan inside a task folder:
process/general-plans/active/{slug}_{date}/{slug}_PLAN_{date}.md(orprocess/features/{feature}/active/{slug}_{date}/{slug}_PLAN_{date}.md). Create the{slug}_{date}/subfolder first. Per task-folder artefact colocation, every artefact this plan produces — the plan, any{slug}_SPEC_{date}.md, reports, and references — lives INSIDE this same task folder; never write to the deprecated siblingreports/orreferences/dirs. - Read
process/context/all-context.mdwhen present to choose relevant context docs. - For complex plans, read
.claude/skills/vc-generate-plan/references/example-complex-prd.mdbefore writing. - Include automated and manual verification gates from
process/context/tests/all-tests.md. - For new or newly touched direct
*_PLAN_*.mdplans, include explicit sections forTouchpoints,Public Contracts,Blast Radius,Verification Evidence,Test Infra Improvement Notes, andResume and Execution Handoff. - Keep resume/dependency notes Markdown-structured for now; do not invent a second machine-only schema.
- If the work is a large multi-phase program, create or update a feature folder plan set:
- one umbrella/orchestration plan
- one direct plan file per phase
- one durable report destination per phase
- Validate the generated artifact:
node .claude/skills/vc-generate-plan/scripts/validate-plan-artifact.mjs <plan-path>
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 80 lines · 38 tokens per session scan A fa89e0e8e37b
vc-generate-plan is a skill published in the GitHub repository withkynam/vibecode-pro-max-kit (1,116 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 1,212 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 skills, from other repositories
new-skill
Scaffold a new custom SKILL.md file interactively. Use when asked to create a new skill or slash command.
gh-issue
Create, view, list, or comment on GitHub issues. Use when asked to file, open, or manage GitHub issues.
gh-pr
Create, review, or manage GitHub pull requests. Use when asked to open, check, or merge a PR.
branch
Create or switch to a feature branch, typically tied to a GitHub issue. Use when asked to create a branch or start work on an issue.
changelog
Generate a changelog or release notes from recent git history. Use when asked to write a changelog, summarize recent commits, or produce release notes.
lint
Run the linter, auto-fix what's fixable, and report the rest. Use when asked to lint or fix lint errors.