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.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/withkynam/vibecode-pro-max-kit/vc-intent-clarifynpx skills add withkynam/vibecode-pro-max-kit --skill vc-intent-clarifygit 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-intent-clarify)<a href="https://agentmods.dev/skills/withkynam/vibecode-pro-max-kit/vc-intent-clarify"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-intent-clarify.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 | $0.00042 | $0.05907 |
| Opus 5 | $0.00021 | $0.02953 |
| Sonnet 5 | $0.00008 | $0.01181 |
| Haiku 4.5 | $0.00004 | $0.00591 |
Grade A, and why
vc-intent-clarify 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 5d 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 — 610 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vc-intent-clarify
Output style: lead each question with the recommended option; plain language, no filler —
process/development-protocols/communication-standards.md.
Two-mode intent clarification: SIMPLE (direct, 3-5 reads) and DEEP (research subagent first, then questions).
Scores a user request's ambiguity and — when Tier 2 triggers — produces a structured, multi-dimension clarification suite with option-rich questions rather than open-ended prompts. Uses vc-scenario, vc-predict, and vc-sequential-thinking style reasoning to generate questions, not just to answer them.
This is the highest-leverage skill in the system. Poor intent clarification wastes entire phase programs. Invest in the question generation step.
When To Invoke
At ORCHESTRATOR before every routing decision for new user requests. Check auto-skip conditions first. If none apply, score the four signals and act on the resulting tier.
Auto-Skip Conditions
These conditions force Tier 0 regardless of the ambiguity score. Check these FIRST.
- Continuation phrases — "go", "continue", "proceed", "just do it", or similar standalone instruction
- Mid-phase-program execution — active phase plan is selected and approved, user is advancing
- Trivial fix — single-file, under 15 lines, no schema/API/auth changes
- Explicit mode command — "ENTER EXECUTE MODE", "ENTER RESEARCH MODE", etc.
- Resuming active plan — an existing active plan is identified and confirmed
- Pure information question — "What is X?", "How does Y work?" mapping to a single obvious routing target
When an auto-skip condition matches, produce only a 1-sentence restatement of intent and route immediately per the existing routing protocol. Do not announce the tier. Do not surface any questions.
Priority ordering when multiple conditions match simultaneously:
- Explicit mode command (highest priority)
- /goal mid-program execution
- Continuation phrase
- Trivial fix / active-plan resume (lowest priority)
- Pure information question / resuming active plan (lowest priority — treated as Tier 0, auto-route to vc-research-agent or answer directly)
What ships with it
3 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.
- 5d ago First seen · 610 lines · 42 tokens per session scan A 3ffff3950fb3
vc-intent-clarify is a skill published in the GitHub repository withkynam/vibecode-pro-max-kit (1,114 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 5,907 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
implement
End-to-end workflow for taking MCP work items from backlog to merged PR. Handles git branching, schema-driven planning, implementation, independent review, and PR creation. Composes spec-quality, review-quality, and schema-workflow skills into a single pipeline. Use when a user says "implement this", "work on this…
session-retrospective
Analyzes the current implementation run — evaluates schema effectiveness, delegation alignment, note quality, and plan-to-execution fit. Captures cross-session trends and proposes improvements when patterns repeat. Use after implementation runs, or when user says 'retrospective', 'session review', 'what did we learn'…
quick-start
Interactive onboarding for the MCP Task Orchestrator. Detects empty or populated workspaces and walks through how plan mode, persistent tracking, and the MCP work together. Use when a user says "get started", "how do I use this", "quick start", "first time setup", "onboard me", "what can this MCP do", or "help me…
ralph
Launcher for the Ralph-style queue drain script — emits the right node ralph-loop.mjs invocation based on the user's filter and bounds. The actual loop runs as a Node script that spawns one claude -p --worktree per iteration; this skill is the configurator, not the loop. Use when a user says: drain the backlog, ralph…
review-proposals
Triages pending improvement-proposal MCP items — presents each with its scope and evidence, collects an accept/reject/defer decision per proposal, and carries out the disposition: project-scoped acceptances get their exact YAML applied to .taskorchestrator/config.yaml and pushed per-root; global acceptances get a…
work-summary
Generates a project dashboard from MCP work items. Default is a lean, attention-first view: what's in flight, what's blocked, what to do next, what's queued. Use when the user says: project status, what's active, show me the dashboard, work summary, what should I work on, project health, what's blocked, where did I…