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-publish/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-publish)<a href="https://agentmods.dev/skills/withkynam/vibecode-pro-max-kit/vc-publish"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-publish.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.1 | $0.00038 | $0.05002 |
| Opus 5 | $0.00019 | $0.02501 |
| Sonnet 5 | $0.00008 | $0.01000 |
| Haiku 4.5 | $0.00004 | $0.00500 |
Grade D, and why
vc-publish scanned grade D with 2 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 6d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
actual_skills=$(ls -d <kitRepoPath>/.claude/skills/vc-*/ | wc -l | tr -d ' ') Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/vc-kit-verify-$TS How it starts
The opening of the file, as written. The whole thing — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vc-publish
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Push harness improvements from the current development repo to the remote kit repository (vibecode-pro-max-kit). This is the maintainer counterpart to vc-update.
vc-update= user pulls latest harness INTO their project FROM the remotevc-publish= maintainer pushes improvements FROM the development repo TO the remote kit repo
Prerequisites
- Local checkout of the kit repo (
git clone [email protected]:withkynam/vibecode-pro-max-kit.git) .vc-publish-configfile in the current repo root (see Configuration below)- Git push access to the remote kit repo
Configuration
Create .vc-publish-config in the repo root:
{"kitRepoPath": "/path/to/vibecode-pro-max-kit"}
If this file is missing, ask the user for the kit repo checkout path and offer to create it.
Workflow
Step 1: Load Configuration
- Read
.vc-publish-configfrom the current repo root. - If missing, ask the user for the kit repo local checkout path.
- Verify the path exists and contains
vc-manifest.json. - Verify the kit repo worktree is clean (
git -C <kitRepoPath> status --porcelain). If dirty, warn and ask whether to proceed or abort.
Step 2: Read Manifest
- Read
vc-manifest.jsonfrom the kit repo checkout. - Extract the current
version. - Before computing a version bump, check if the current kit version already matches the intended target version (e.g.
3.0.0). If the kitversionalready equals the target: skip the bump step entirely and proceed directly to Step 3 with atag-as-isnote — do not increment the version. Record in the publish summary that the version was unchanged.
Catalog-regen (pre-publish): Before resolving files in Steps 3–4, regenerate the skills catalog in the dev repo:
node .claude/skills/vc-audit-context/scripts/generate-skills-catalog.mjs --write
This ensures process/context/generated-skills-catalog.json is current before it is copied into the kit repo.
What ships with it
1 file 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.
- 6d ago First seen · 374 lines · 38 tokens per session scan D 4d808a9d4442
vc-publish is a skill published in the GitHub repository withkynam/vibecode-pro-max-kit (1,116 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 5,002 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 2 findings (enumerates other installed skills, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
release-revoke
Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish…
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
generate-release-notes
Generate categorized release notes from any source (GitHub, Linear, Jira, or manual input) with optional publishing.