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.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/instructions/withkynam/vibecode-pro-max-kit/claude-md)<a href="https://agentmods.dev/instructions/withkynam/vibecode-pro-max-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/withkynam/vibecode-pro-max-kit/claude-md/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/instructions/withkynam/vibecode-pro-max-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/withkynam/vibecode-pro-max-kit/claude-md.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.06795 | $0.06795 |
| Opus 5.5 | $0.02718 | $0.02718 |
| Sonnet 5.5 | $0.01359 | $0.01359 |
| Haiku 4.5 | $0.00679 | $0.00679 |
Grade A, and why
vibecode-pro-max-kit CLAUDE.md 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 — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Bootstrap Guard
If process/context/all-context.md does not exist, the harness has not been set up yet. (Note: process/context/ itself may already hold only generated-skills-catalog.json from install — that alone does NOT count as set up.) Run vc-setup before any task — the context router, protocol docs, and the validator suite are absent and agents will not route correctly.
Before Any Substantial Task
Always run:
find process/context/ -type f
find process/development-protocols/ -type f
Mandatory gate: Do not proceed to load any context file until both find commands have run and their full output has been read. Substituting ls for find -type f is a protocol violation — ls misses subdirectories and dotfiles, producing an incomplete file listing. Run the exact commands above, read their output, then proceed.
Then read @process/context/all-context.md and @process/development-protocols/all-development-protocols.md.
Follow their routing tables to load the specific files relevant to your task. Never hardcode file paths — always discover from the listing.
See process/context/all-context.md for project-specific coding preferences and conventions.
RIPER-5 Spec-Driven Development System
This project uses RIPER-5 methodology for systematic, spec-driven development. RIPER-5 prevents premature implementation and ensures quality through strict mode-based workflows.
Shared Development Protocols
Canonical shared workflow rules live in process/development-protocols/. Read order and per-file
roles: @process/development-protocols/all-development-protocols.md (router — now discoverable via
frontmatter). Notable sections: orchestration.md §Two-Tier Fan-Out (vc-agent-strategy-compare)
and §Intent Clarification (vc-intent-clarify).
Reference docs (harness methodology, not project-specific):
.claude/skills/vc-generate-plan/references/example-simple-prd.md- Reference for simple plan structure.claude/skills/vc-generate-plan/references/example-complex-prd.md- Reference for complex plan depth.claude/skills/vc-generate-phase-program/references/program-goal-charter-template.md- Program Goal Charter template for phase programs
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 · 441 lines · 6,795 tokens per session scan A 9c0b94386e68
vibecode-pro-max-kit CLAUDE.md is an instructions file published in the GitHub repository withkynam/vibecode-pro-max-kit (1,155 stars, last pushed 4mo ago), licensed MIT. It adds 6,795 tokens to every session, about $0.0272 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.