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-generate-contextnpx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-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-generate-context)<a href="https://agentmods.dev/skills/withkynam/vibecode-pro-max-kit/vc-generate-context"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-generate-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.00035 | $0.00723 |
| Opus 5 | $0.00017 | $0.00362 |
| Sonnet 5 | $0.00007 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
vc-generate-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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate 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 maintain process/context/all-context.md, the broad portable project knowledge layer shared by Codex and Claude. Use process/context/all-context.md as the context router before reading grouped docs.
Optional input: a package, app, feature, context group, or architectural area to refresh first.
Workflow
- Read
references/generate-context.mdfor the full context contract. - Determine mode:
- Full scan when
process/context/all-context.mdis missing. - Delta update when it exists.
- Full scan when
- Read
process/context/all-context.mdwhen present to identify relevant grouped context files. - Inspect current repo state, active plans, feature folders, package scripts, tooling, important architecture files, and relevant
process/context/**/*.mddocs. - Produce
process/context/all-context.mdPLUSprocess/context/{group}/all-{group}.mdfor each detected or approved group (see Invocation Modes below). - Include scan timestamp, repo HEAD if available, changes since last update, open questions, and source references.
- Validate the generated context:
node .claude/skills/vc-generate-context/scripts/validate-all-context.mjs - If routing or grouped context changed, also run:
node .claude/skills/vc-audit-context/scripts/validate-context-discovery.mjs
Rules
- Treat
process/context/as durable cross-agent knowledge. - Treat
process/context/all-context.mdas the durable routing protocol; do not replace it with generated prose. - Do not store agent-specific mechanics here unless they affect project workflow.
- Do not rewrite grouped context docs; if they are stale or mis-grouped, flag
audit-context. - Prefer concise, factual, path-specific documentation.
- Use
pnpmterminology for package management. - Treat validation failures as blockers before presenting context as refreshed.
What ships with it
2 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.
- 5d ago First seen · 57 lines · 35 tokens per session scan A 18f86239ab86
vc-generate-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 35 tokens to every session and 723 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
align-context
Update all context files (task, spec, task-context, worklog) to reflect current state of work — fixes stale entries, fills missing knowledge, reports what changed.
context-handoff
Generate a context handoff document at the end of a session so the next session can pick up where this one left off. Auto-invoked when ending significant work, or manually via /handoff.
task-agent-eliza-bridge
Use when spawning a Claude Code, Codex, Gemini, Aider, or other CLI task agent whose work needs parent Eliza runtime context. Covers the read-only loopback bridge for character, room, memory, and active workspace state.
kb-builder
Build an Obsidian-compatible knowledge base from public web sources using the TinyFish CLI. Use this skill when a user wants a builder-grade markdown knowledge base on a technical topic, asks for a structured research vault, or wants a topic compiled from live public sources into interlinked markdown files. Supports…
weknora-shared
Use when driving a WeKnora RAG server through the weknora CLI as an agent — authenticating, managing knowledge bases / documents / sessions / agents, running search or chat, or interpreting the CLI's JSON envelopes and exit codes. Read this before any other weknora- skill.
02-project-memory
Build the project's memory of its architecture, conventions, and decisions, and wire it into your AI tools. Use when the user wants to set up or refresh project memory, or rewire it into a tool. Not for editing one existing memory file.