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 agents/withkynam/vibecode-pro-max-kit/vc-update-process-agentgit clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kitWhat 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.00036 | $0.11980 |
| Opus 5 | $0.00018 | $0.05990 |
| Sonnet 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 yesterday.
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.
- yesterday 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,105 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 11,980 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 agents, from other repositories
orchestrator
Autonomous operations manager — coordinates AI agent roles to execute tasks through PLAN→BUILD→TEST→VERIFY→SHIP pipeline with minimal human involvement.
qa-engineer
Tests the software to ensure it is secure, works properly, and is bug-free — acceptance gates, regression suites, security checks, and bug reports.
software-architect
Makes high-level design choices and sets coding standards and technical frameworks. Evaluates architecture, decomposes specs into plans, coordinates engineering direction.
ai-ml-engineer
Builds, trains, and optimizes machine learning models and AI tools — model selection, prompts, evaluation, and integration.
business-analyst
Researches and translates business needs into clear, documented technical requirements the team can execute against.
devops-engineer
Connects development and IT operations to automate software deployment and manage infrastructure — CI/CD, IaC, releases, and environment reliability.