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-audit-plans/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-audit-plans)<a href="https://agentmods.dev/skills/withkynam/vibecode-pro-max-kit/vc-audit-plans"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-audit-plans.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.00040 | $0.00697 |
| Opus 5 | $0.00020 | $0.00349 |
| Sonnet 5 | $0.00008 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
vc-audit-plans 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Plans
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 review active plan artifacts and reconcile them with the current codebase.
This is a maintenance and recovery skill, not an automatic post-task hook.
Optional input: a feature, folder, plan filename, or maintenance scope to prioritize.
Prefer it when:
- UPDATE PROCESS was skipped and active-plan cleanup drift accumulated
- the user wants a periodic active-plan cleanup pass
- multiple active plans need reconciliation after a burst of work
Workflow
- Read
references/audit-plans.mdfor the full audit process. - Run the inventory validator:
node .claude/skills/vc-audit-plans/scripts/validate-plan-inventory.mjs - Inventory plans in
process/general-plans/active/andprocess/features/*/active/. Plans now live inside{slug}_{date}/task subfolders — scan one level deep. Do NOT count_REPORT_,_REF_, or_SPEC_files inside task folders as plans; only_PLAN_files count. For feature-scoped audits, first runfind process/features/{feature}/ -type f | sortfor full artifact visibility. For full audits, runfind process/features/ -type f | sortto see all feature artifacts across all subdirs (active, completed, backlog, references, reports). 3.5. Scan task folder contents (co-located REPORT/REF/SPEC files) alongside each plan. Per task-folder artefact colocation, the correct home for every artefact (plan, spec, reports, references) is INSIDE its{slug}_{date}/task folder; flag any task artefact found in the deprecated siblingreports//references/dirs or any ad-hoc location as mis-located, and recommend moving it into the owning task folder. Match by feature slug, date proximity (7 days), or content reference to the plan filename. - Cross-check each plan against the actual codebase with file existence checks and targeted
rgsearches. - Classify each plan as
Completed,Partially Done,Obsolete,Stale,Active, orReference. - Move only clearly completed or obsolete plans to the appropriate
completed/folder. Usegit mv active/{slug}_{date}/ completed/{slug}_{date}/— move the WHOLE task folder; nocompleted_prefix added. - Ask before deleting anything.
- Re-run the inventory validator after moving or editing plan files.
What ships with it
17 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-plans.md 4.7 KB
- scripts/eval-coverage-known-gaps.json 7.6 KB
- scripts/fixtures/validate-backlog-notes/fail/malformed_NOTE.md 137 B
- scripts/fixtures/validate-backlog-notes/pass/d2-fix-deferred_NOTE.md 268 B
- scripts/fixtures/validate-phase-plan-completeness/fail.md 246 B
- scripts/fixtures/validate-phase-plan-completeness/pass.md 307 B
- scripts/fixtures/validate-phase-reports/fail/umbrella.md 327 B
- scripts/fixtures/validate-phase-reports/pass/phase-01_REPORT.md 71 B
- scripts/fixtures/validate-phase-reports/pass/umbrella.md 327 B
- scripts/fixtures/validate-umbrella-state/fail.md 397 B
- scripts/fixtures/validate-umbrella-state/pass.md 404 B
- scripts/validate-backlog-notes.mjs 2.0 KB runs code
- scripts/validate-eval-coverage.mjs 9.7 KB runs code
- scripts/validate-phase-plan-completeness.mjs 1.6 KB runs code
- scripts/validate-phase-reports.mjs 3.5 KB runs code
- scripts/validate-plan-inventory.mjs 3.8 KB runs code
- scripts/validate-umbrella-state.mjs 3.3 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.
- 8d ago First seen · 48 lines · 40 tokens per session scan A c1084e122cb1
vc-audit-plans is a skill published in the GitHub repository withkynam/vibecode-pro-max-kit (1,117 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 697 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
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.