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-autopilotnpx skills add withkynam/vibecode-pro-max-kit --skill vc-autopilotgit 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-autopilot)<a href="https://agentmods.dev/skills/withkynam/vibecode-pro-max-kit/vc-autopilot"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-autopilot.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.00034 | $0.01121 |
| Opus 5 | $0.00017 | $0.00561 |
| Sonnet 5 | $0.00007 | $0.00224 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
vc-autopilot 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vc-autopilot
Contract skill that owns the provisional goal block artifact for Autopilot Mode sessions. This skill is invoked by the orchestrator to emit, validate, and resume from the goal block. The canonical protocol lives in process/development-protocols/autopilot.md.
When To Invoke
Invoke this skill when:
- The orchestrator has just received an autopilot trigger phrase and needs to emit the provisional goal block after the consolidated clarification round.
- The orchestrator detects a pasted goal block at session start and needs to determine whether it is a resume scenario (goal block already present → no new clarification round).
- The
validate-autopilot-goal-block.mjsD1 validator needs to be run against an artifact.
Skill Artifact
The provisional goal block — a structured text block of ≤ 4000 characters with exactly 9 named fields. The canonical field spec lives in process/development-protocols/autopilot.md §Provisional Goal Block Format. This skill does not redefine the spec — it references it.
Required fields (exact string anchors — do not rename or abbreviate):
SESSION GOAL:ENTRY PHASE:REMAINING PHASES:CLARIFICATIONS LOCKED:EXECUTE CONSENT:— must contain the literal textstanding-grantedDECISION POLICY:HARD STOPS:TEST GATES:START:
Emission Procedure
Step-by-step for the orchestrator:
- Complete the consolidated clarification round (
process/development-protocols/autopilot.md §Consolidated Clarification Round). - Determine
ENTRY PHASEfrom on-disk artifact detection (autopilot.md §Trigger-Anywhere Detection Flow). - Build the
REMAINING PHASESchecklist: for each phase not yet complete in canonical RIPER-5 order, add a[ ]checkbox line with the phase name and planned execution strategy. - Fill in all 9 fields using the locked clarification answers.
- Count total characters. If > 4000: compress DECISION POLICY and CLARIFICATIONS LOCKED to summaries and reference autopilot.md for full detail.
- Print the block to chat as a fenced code block.
- Write the block to disk:
{task-folder}/{slug}_AUTOPILOT_GOAL_{dd-mm-yy}.md(header: "Emitted: [datetime]. Provisional block. V7 will emit (UPDATE) variant."). - Emit
AUTOPILOT_ACTIVATED: [task] — entry phase: [phase] — goal block emitted.
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.
- 6d ago First seen · 99 lines · 34 tokens per session scan A 4e5d81a2cb90
vc-autopilot is a skill published in the GitHub repository withkynam/vibecode-pro-max-kit (1,114 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 1,121 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'…
adopt-project-scope
Migrates an already-populated, unscoped Task Orchestrator database in place to the project-scoping convention — creates a project anchor root, re-parents existing work trees under it, and writes rootId back to config.yaml. Use when a user says: adopt project scope, migrate this database to project scoping, make this…
dependency-manager
Visualizes, creates, and diagnoses dependencies between MCP work items. Use when a user says: what blocks this, add a dependency, show dependency graph, why can't this start, link these items, unblock this, remove dependency, or show blockers.
manage-schemas
Creates, views, edits, deletes, and validates note schemas for the MCP Task Orchestrator in .taskorchestrator/config.yaml — the templates that define which notes agents must fill at each workflow phase. Also recommends schema designs from a library of workflow patterns (autonomous coding loops, spec-driven teams…
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…