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-agent-strategy-compare/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-agent-strategy-compare)<a href="https://agentmods.dev/skills/withkynam/vibecode-pro-max-kit/vc-agent-strategy-compare"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-agent-strategy-compare.svg" alt="Measured on agentmods" 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.00052 | $0.04850 |
| Opus 5 | $0.00026 | $0.02425 |
| Sonnet 5 | $0.00010 | $0.00970 |
| Haiku 4.5 | $0.00005 | $0.00485 |
Grade A, and why
vc-agent-strategy-compare 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 8d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vc-agent-strategy-compare
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Evaluate 4 execution strategies for any RIPER-5 phase or fan-out task. Computes the 7-signal score, shows explicit agent count math, applies cost guards, and outputs a ranked strategy recommendation.
All strategies use the existing vc-system agents and skills. The question is only how they are orchestrated.
Model Selection Policy
Every spawned agent — across ALL four strategies (sequential, parallel subagents, dynamic workflow, agent team) — defaults to sonnet. Spawn opus ONLY when the agent is carrying out real source-code or build execution (writing/editing code, running builds, applying migrations). Planning, research, analysis, validation, review, and synthesis all run on sonnet.
Concrete rules:
- Default = sonnet for any teammate, parallel subagent, or
agent()call in a workflow. State the model explicitly when spawning. - opus ONLY for execution work: the agent that actually implements code (the vc-execute-agent leg, or a workflow
agent()step whose job is to modify source / run a build). The RIPER-5 phase that runs on opus is EXECUTE; all other phases (RESEARCH, SPEC, INNOVATE, PLAN, VALIDATE, UPDATE PROCESS) run on sonnet. - Agent-team members: assign sonnet to reviewers, researchers, validators, and planners; assign opus only to the teammate doing real code execution.
- Dynamic workflows: pass
model: 'sonnet'onagent()calls by default; passmodel: 'opus'only on the execution stage that writes code or runs builds. - Parallel subagents: fan-out investigation/review subagents are sonnet; only an implementing subagent is opus.
Rationale: opus is reserved for the one place judgment-under-execution materially changes code quality. Everything upstream is sonnet-cheap without quality loss, and this keeps fan-outs (which multiply agent count) on the cost-efficient tier. This mirrors the live agent frontmatter: vc-execute-agent, vc-fast-mode-agent, and vc-quick-fix-agent are opus; every other vc-agent is sonnet.
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.
- 8d ago First seen · 285 lines · 52 tokens per session scan A c38acfe58763
vc-agent-strategy-compare is a skill published in the GitHub repository withkynam/vibecode-pro-max-kit (1,117 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 4,850 once invoked, about $0.0003 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
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.
run-tests
Run the project test suite and surface failures. Use when asked to run tests or check test status.
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.