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-audit-contextnpx skills add withkynam/vibecode-pro-max-kit --skill vc-audit-contextgit 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-audit-context)<a href="https://agentmods.dev/skills/withkynam/vibecode-pro-max-kit/vc-audit-context"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-audit-context.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.00037 | $0.01085 |
| Opus 5 | $0.00018 | $0.00543 |
| Sonnet 5 | $0.00007 | $0.00217 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
vc-audit-context 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Context
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Use this skill to verify that the project's durable context layer is discoverable and organized.
Optional input: a context group, agent, skill, or folder scope to prioritize during the audit.
Workflow
- Run
find process/context/ -type f | sortto get the full file listing before routing. This ensures no context file is silently skipped when the router is incomplete or drifted. - Read
process/context/all-context.mdfor the context routing protocol. - Read
references/audit-context.mdfor the full audit process. - Run the context discovery validator:
node .claude/skills/vc-audit-context/scripts/validate-context-discovery.mjs
3a. Run the protocol discovery frontmatter validator (enforces discovery frontmatter on every
process/development-protocols/**/*.md, recursive incl. vc-system-behavior/; note.md is the
only intentional exclusion):
node .claude/skills/vc-audit-context/scripts/validate-protocol-discovery.mjs
- Run the shared skill routing coverage validator:
node .claude/skills/vc-audit-context/scripts/validate-skill-routing.mjs - Run the skill cross-reference validator:
node .claude/skills/vc-audit-context/scripts/validate-skill-cross-refs.mjs - Run the skill dependency/confusable analysis:
node .claude/skills/vc-audit-context/scripts/validate-skill-dependencies.mjs node .claude/skills/vc-audit-context/scripts/validate-confusable-skills.mjs - Regenerate or check the machine-readable skill catalog:
node .claude/skills/vc-audit-context/scripts/generate-skills-catalog.mjs --write node .claude/skills/vc-audit-context/scripts/generate-skills-catalog.mjs --check - Validate that every SKILL.md carries
trigger_keywords+ a validlayer(contract|helper) and that the catalog is in sync:node .claude/skills/vc-audit-context/scripts/validate-skill-keywords.mjs - If any script reports failures, inspect the referenced files and patch the smallest relevant surface.
- Re-run the failed validators until they pass.
What ships with it
11 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.
- references/audit-context.md 5.3 KB
- references/skill-routing-policy.json 153 B
- scripts/generate-skills-catalog.mjs 2.2 KB runs code
- scripts/shared-skill-utils.mjs 5.3 KB runs code
- scripts/validate-confusable-skills.mjs 1.3 KB runs code
- scripts/validate-context-discovery.mjs 15 KB runs code
- scripts/validate-protocol-discovery.mjs 4.0 KB runs code
- scripts/validate-skill-cross-refs.mjs 820 B runs code
- scripts/validate-skill-dependencies.mjs 1.2 KB runs code
- scripts/validate-skill-keywords.mjs 2.0 KB runs code
- scripts/validate-skill-routing.mjs 3.4 KB runs code
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 · 85 lines · 37 tokens per session scan A f467fe8b5b63
vc-audit-context is a skill published in the GitHub repository withkynam/vibecode-pro-max-kit (1,114 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 1,085 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'…
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…
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…
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…