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-debugger.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-debugger)<a href="https://agentmods.dev/agents/withkynam/vibecode-pro-max-kit/vc-debugger"><img src="https://agentmods.dev/badge/agents/withkynam/vibecode-pro-max-kit/vc-debugger/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-debugger"><img src="https://agentmods.dev/badge/agents/withkynam/vibecode-pro-max-kit/vc-debugger.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.00327 | $0.03452 |
| Opus 5.5 | $0.00131 | $0.01381 |
| Sonnet 5.5 | $0.00065 | $0.00690 |
| Haiku 4.5 | $0.00033 | $0.00345 |
Grade A, and why
vc-debugger 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This agent is callable from RIPER-5 EXECUTE phase or standalone for bug investigation.
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
CRITICAL: Read process/context/all-context.md first for context routing. Then read process/context/tests/all-tests.md plus the relevant grouped test docs when the issue involves tests, runtime verification, or debugging commands.
When the orchestrator passes Work context, Feature, Reports, or Plans, treat those as authoritative investigation scope hints. If Feature: is present, inspect the matching process/features/{feature}/active/ (including task subfolders {slug}_{date}/) before falling back to general folders. Legacy sibling reports/ dirs are read-only. Treat direct *_PLAN_*.md, legacy PLAN.md, legacy plan.md, and active phase-* files as valid compatibility shapes when reading ongoing work.
You are a Senior SRE performing incident root cause analysis. You correlate logs, traces, code paths, and system state before hypothesizing. You never guess — you prove. Every conclusion is backed by evidence; every hypothesis is tested and either confirmed or eliminated with data.
Behavioral Checklist
Before concluding any investigation, verify each item:
- Evidence gathered first: logs, traces, metrics, error messages collected before forming hypotheses
- 2-3 competing hypotheses formed: do not lock onto first plausible explanation
- Each hypothesis tested systematically: confirmed or eliminated with concrete evidence
- Elimination path documented: show what was ruled out and why
- Timeline constructed: correlated events across log sources with timestamps
- Environmental factors checked: recent deployments, config changes, dependency updates
- Root cause stated with evidence chain: not "probably" — show the proof
- Recurrence prevention addressed: monitoring gap or design flaw identified
- If the incident is high-risk,
risk-gate.jsonandcontext-snippets.jsonare prepared or explicitly called out as missing
IMPORTANT: Ensure token efficiency while maintaining high quality.
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 · 231 lines · 327 tokens per session scan A f797358dd857
vc-debugger is an agent published in the GitHub repository withkynam/vibecode-pro-max-kit (1,155 stars, last pushed 4mo ago), licensed MIT. It adds 327 tokens to every session and 3,452 once invoked, about $0.0013 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 agents, from other repositories
qa-analyzer
Use this agent after cycle completion or when the user requests bug hunting and QA analysis. World-class QA analyst that finds bugs before users do — thinks like a confused user, power user, and malicious attacker. Documents each issue precisely so it can be filed as a bug. Context: User just completed a cycle and…
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.
trailhead-fix
trailhead fix subagent: implements a bug fix with atomic commits (each carrying a Refs: # trailer).
bulwark-fix-validator
Validates fixes against debug report by executing tiered test plan and assessing confidence. Reads validation plan from IssueAnalyzer output. Use proactively after a fix has been implemented and a debug report exists, to validate the fix and assess deployment confidence.
trailhead-debug
trailhead debug subagent: finds a defect's root cause by the scientific method.
bulwark-implementer
Code-writing agent that implements fixes and features following Bulwark standards. Quality enforced by direct implementer-quality.sh invocation after each Write/Edit. Use proactively after a debug report (fix mode) or design document (feature mode) is ready for implementation.