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-spec/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-spec)<a href="https://agentmods.dev/skills/withkynam/vibecode-pro-max-kit/vc-generate-spec"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-generate-spec/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-generate-spec"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-generate-spec.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.00043 | $0.01274 |
| Opus 5.5 | $0.00017 | $0.00510 |
| Sonnet 5.5 | $0.00009 | $0.00255 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
vc-generate-spec 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate SPEC
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Use this skill to produce the authoritative product-discovery SPEC artifact for a task — a plain-language requirements document written for user review, not for an engineer.
A SPEC captures what the user wants and why so the user can read it, recognize their own intent, and confirm "yes, build that" before any approach or code is chosen. It is the bridge between RESEARCH (the facts) and INNOVATE (the how). PLAN cannot start until a SPEC exists for non-trivial work.
SPEC consumes: RESEARCH findings + the user's stated intent/brainstorm. It does NOT consume a chosen approach or a Decision Summary — no approach exists yet at SPEC time.
Normal output is one SPEC file: {slug}_SPEC_{dd-mm-yy}.md.
For a phase program, the program-level (umbrella) SPEC is written once during the outer loop and governs every inner phase. Use templates/program-spec-template.md for that case. The inner loop never writes a SPEC.
Workflow
- Read
references/spec-contract.mdfor the full section-by-section writing rules. - Run
date +%d-%m-%ybefore choosing the filename. - Confirm the inputs are present: RESEARCH findings + the user's stated intent. If neither is present, emit
SPEC_INTENT_BLOCKEDinstead of writing. - Read
process/context/all-context.mdfirst, then load the relevant context group. When the work touches testing/verification, readprocess/context/tests/all-tests.mdso acceptance-criteria scenarios are grounded in the real test-context chain. - Save the SPEC inside the task folder alongside the plan:
process/features/{feature}/active/{slug}_{date}/{slug}_SPEC_{date}.md(orprocess/general-plans/active/{slug}_{date}/{slug}_SPEC_{date}.md). For a phase program, the umbrella task folder holds{program-slug}_SPEC_{date}.md. Per task-folder artefact colocation, never write to the deprecated siblingreports/orreferences/dirs. - Write the SPEC sections in canonical order (see
references/spec-contract.md):## Summary## User Stories / Jobs To Be Done## What The User Wants (Behavioral Outcomes)## Flow / State Diagram(ASCII)## Acceptance Criteria (Testable Outcomes)— each criterion carriesproven by:+strategy:## Out Of Scope## Constraints## Open Questions## Background / Research Findings
- Keep the document oriented for user review: plain language, no file paths, no library names, no schema or code. Anything engineer-only moves to Background or a later phase.
- Each acceptance criterion MUST be provable by comprehensive tests, with a fully-automated E2E/integration gate wherever the behavior is automatable. Agent-Probe / Known-Gap stand only as an explicitly-justified residual. Vacuous-green is banned.
- If
## Open Questionsis non-empty at finalize (interactive session): emitSPEC_INTENT_BLOCKEDand stop. Under /goal: record each as a backlog note and continue. - Once Open Questions is empty/"None" (or backlogged under /goal): save the file and the agent emits
PHASE_COMPLETE: SPEC.
What ships with it
2 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 · 72 lines · 43 tokens per session scan A be89c067223a
vc-generate-spec is a skill published in the GitHub repository withkynam/vibecode-pro-max-kit (1,155 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 1,274 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.