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-plan-discovery/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-plan-discovery)<a href="https://agentmods.dev/skills/withkynam/vibecode-pro-max-kit/vc-plan-discovery"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-plan-discovery/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/skills/withkynam/vibecode-pro-max-kit/vc-plan-discovery"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-plan-discovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.00904 |
| Opus 5.5 | $0.00016 | $0.00362 |
| Sonnet 5.5 | $0.00008 | $0.00181 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
vc-plan-discovery 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vc-plan-discovery
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Invocation
Primary method — run the auto-discovery script. It applies the Scope Rules below
(same-feature full depth; other features active-only; general-plans active always) and
extracts ONLY the leading YAML frontmatter block of each .md file (no whole-file reads):
node .claude/skills/vc-plan-discovery/scripts/discover-plans.mjs [--feature <name>] [--json]
It groups output into Active Plans / Backlog / Completed / Reports / References (each line:
- [name]: description (path)) and prints a trailing Found N active, N backlog, N completed, N reports, N references line. It never throws on a missing root and exits 0
unless given a bad flag. Use --json for a machine-readable object. Prefer this over the
manual scan below — it is deterministic and avoids loading huge files into context.
Per task-folder artefact colocation, the script scans one level into each
{slug}_{date}/ task folder and surfaces co-located _PLAN_/_REPORT_/_REF_ artefacts;
the sibling reports//references/ dirs are deprecated and only hold legacy artefacts.
The manual scan in Scope Rules below is the FALLBACK for when the script fails.
Purpose
Surface all plans relevant to the current task so agents have full plan context — what was tried, what is in progress, what is deferred, and what reports and references exist — before doing any phase work.
Scope Rules
- Same feature folder (from task context or argument): read ALL of
active/,backlog/,completed/, plus any legacy siblingreports/,references/— surface every file with frontmatter - Other feature folders: read
active/only — surface plans whose frontmatterdescriptionorfeaturefield matches the task domain general-plans/active/: always scangeneral-plans/completed/, legacyreports/,references/: scan only when same-feature folder is not identified
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.
- 1mo ago First seen · 86 lines · 39 tokens per session scan A 9177943a600b
vc-plan-discovery is a skill published in the GitHub repository withkynam/vibecode-pro-max-kit (1,155 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 904 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 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.