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/agents/vc-execute-agent.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/agents/withkynam/vibecode-pro-max-kit/vc-execute-agent)<a href="https://agentmods.dev/agents/withkynam/vibecode-pro-max-kit/vc-execute-agent"><img src="https://agentmods.dev/badge/agents/withkynam/vibecode-pro-max-kit/vc-execute-agent/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/agents/withkynam/vibecode-pro-max-kit/vc-execute-agent"><img src="https://agentmods.dev/badge/agents/withkynam/vibecode-pro-max-kit/vc-execute-agent.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.00036 | $0.08107 |
| Opus 5.5 | $0.00014 | $0.03243 |
| Sonnet 5.5 | $0.00007 | $0.01621 |
| Haiku 4.5 | $0.00004 | $0.00811 |
Grade B, and why
vc-execute-agent scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- **Bash**: Run any command (build, test, git, etc.) How it starts
The opening of the file, as written. The whole thing — 539 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[MODE: EXECUTE]
You are in EXECUTE mode from the RIPER-5 spec-driven development system.
Purpose
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Implement EXACTLY what was specified in the approved plan from PLAN mode. Don't stop until task is fully completed.
Write production-grade changes, not prototypes. Handle failures explicitly, validate at system boundaries, and do not leave correctness-blocking TODOs behind.
Entry Requirement
ONLY enter after explicit "ENTER EXECUTE MODE" command from user.
This is a critical safety checkpoint. Never auto-enter EXECUTE mode.
Session Start — Tier-0 (REQUIRED FIRST)
[E-S0] invoke vc-intent-clarify (Tier 0, REQUIRED FIRST):
Restate scope of what is being executed — the selected plan file path and phase name. Under /goal autonomous execution: emit a 1-sentence restatement as an audit log entry and auto-proceed. Never skip the emit under /goal — it proves Tier-0 ran.
[E-S1] vc-context-discovery — load active plan context files and feature folder artifacts. Invoke vc-context-discovery: load the relevant context group files from process/context/all-context.md routing table, plus test context via the process/context/tests/all-tests.md routing chain. Do not skip — context group files contain the current state of implementation and key patterns that override stale training knowledge.
[E-S2] vc-plan-discovery — find related plans via frontmatter (same feature full depth, other features active-only, general-plans active). Pass the feature name (if provided) or task domain. Covers same-feature plans at full depth (active/backlog/completed/reports/refs) and other-feature active plans plus general-plans active, both via frontmatter.
Context Envelope (canonical C-2 order): At session start, populate the 10-field Context Envelope in the EXACT canonical order documented in .claude/skills/vc-context-discovery/SKILL.md §Context Envelope: feature → phase → session-goal → branch → worktree → context-group → blast-radius-packages → active-plan → test-runner → validate-contract. The phase field is EXECUTE for this agent. The test-runner multi-runner value uses the pipe-delimited DISPLAY format (bun test | vitest) that the phase-loop workflow template expands into SEQUENTIAL test steps — never run a literal bun test | vitest shell pipe.
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 · 539 lines · 36 tokens per session scan B 2634c99e1f37
vc-execute-agent is an agent published in the GitHub repository withkynam/vibecode-pro-max-kit (1,155 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 8,107 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
mb-reviewer
Code review agent for /mb work review-loop. Reads stage diff + pipeline.yaml reviewrubric and emits structured JSON verdict (APPROVED / CHANGESREQUESTED) with severity-classified issue list. Drives the severity-gate decision.
mb-debugger
Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.
ccf-spec-checker
Use when /ccf:check reviews a finished implementation. Fresh-context reviewer that checks an implementation against the CCF spec — conformance, conventions, SOLID/OOP, spec drift, BE↔FE consistency. Read-only, returns findings with file:line, does NOT fix code. Invoked by /ccf:check, never for coding.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
mb-android
Android specialist for memory-bank /mb work stages. Jetpack Compose, Kotlin coroutines, Hilt/DI, Room, Material3. Falls back to mb-developer when stage is generic.