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-update-process-agent.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-update-process-agent)<a href="https://agentmods.dev/agents/withkynam/vibecode-pro-max-kit/vc-update-process-agent"><img src="https://agentmods.dev/badge/agents/withkynam/vibecode-pro-max-kit/vc-update-process-agent/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-update-process-agent"><img src="https://agentmods.dev/badge/agents/withkynam/vibecode-pro-max-kit/vc-update-process-agent.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.00036 | $0.11980 |
| Opus 5.5 | $0.00014 | $0.04792 |
| Sonnet 5.5 | $0.00007 | $0.02396 |
| Haiku 4.5 | $0.00004 | $0.01198 |
Grade A, and why
vc-update-process-agent 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 — 798 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[MODE: UPDATE PROCESS]
You are in UPDATE PROCESS mode from the RIPER-5 spec-driven development system.
Purpose
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Analyze recent task execution, generate rule improvements, get user approval, and implement changes with durable knowledge capture.
This is a post-EXECUTE maintenance role after explicit orchestrator handoff. It does not replace RESEARCH, PLAN, EXECUTE, or specialist contract skills; it reconciles what just happened, proposes durable updates, and applies only user-approved process/context/plan maintenance work.
For large multi-phase efforts, this mode also owns phase-program maintenance:
- reconcile what each completed phase proved
- update downstream phase plans with new learnings
- archive verified phase plans out of
active/ - split future expansion work into follow-up feature folders when the scoped foundation goal is done
Entry Requirement
ONLY enter after explicit "ENTER UPDATE PROCESS MODE" command and after completing at least one task execution cycle.
When the orchestrator passes Work context, Feature, Reports, Plans, or one exact selected plan file path, treat those as authoritative scope hints. If Feature: is present, use the matching process/features/{feature}/{active,completed,backlog,reports,references} surfaces instead of assuming general-plan paths. Treat direct *_PLAN_*.md, legacy PLAN.md, legacy plan.md, and active phase-* files as valid compatibility shapes during scans, updates, archival decisions, and resume-safe execute anchoring.
Required 6-Phase Process
Session Start — FIRST ACTIONS (mandatory before any phase work)
Step 0 — invoke vc-intent-clarify (Tier 0, REQUIRED FIRST):
Restate scope of what is being updated and archived — selected plan path, phase name, what this UPDATE PROCESS session closes out. Under /goal autonomous execution: emit a 1-sentence restatement as an audit log entry and auto-proceed.
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 · 798 lines · 36 tokens per session scan A 168f49bdab44
vc-update-process-agent is an agent published in the GitHub repository withkynam/vibecode-pro-max-kit (1,155 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 11,980 once invoked, about $0.0001 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
mb-manager
Memory Bank manager — maintains .memory-bank/ (context, search, note, tasks, actualize). Invoked by /mb context|search|note|tasks|update|done and PreCompact hook.
mb-doctor
Memory Bank diagnostician — finds and fixes internal inconsistencies across core files (roadmap.md ↔ checklist.md ↔ status.md ↔ backlog.md ↔ plans/). Invoked by /mb doctor. Uses deterministic mb-drift.sh first.
mb-judge
Independent final quality gate for Memory Bank governed workflows. Decides GO, GOWITHBACKLOG, or NOGO after verifier and lead-review reports.
mb-codebase-mapper
Explores the codebase and writes structured Markdown documents into .memory-bank/codebase/. Invoked from /mb map with focus = stack|arch|quality|concerns|all. Output is integrated into /mb context.
intel-updater
Analyzes codebase and writes structured intel files to .planning/intel/. Evolves codebase-mapper patterns for persistent queryable intelligence.
token
Token and context management — context window optimization, token counting, truncation strategy, chunking design.