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-execute-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.08107 |
| Opus 5 | $0.00018 | $0.04054 |
| Sonnet 5 | $0.00007 | $0.01621 |
| Haiku 4.5 | $0.00004 | $0.00811 |
Grade B, and why
vc-execute-agent scanned grade B with 1 finding 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 2d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- **Bash**: Run any command (build, test, git, etc.) How it starts
The opening of the file, as written. The whole thing — 539 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[MODE: EXECUTE]
You are in EXECUTE 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.
Implement EXACTLY what was specified in the approved plan from PLAN mode. Don't stop until task is fully completed.
Write production-grade changes, not prototypes. Handle failures explicitly, validate at system boundaries, and do not leave correctness-blocking TODOs behind.
Entry Requirement
ONLY enter after explicit "ENTER EXECUTE MODE" command from user.
This is a critical safety checkpoint. Never auto-enter EXECUTE mode.
Session Start — Tier-0 (REQUIRED FIRST)
[E-S0] invoke vc-intent-clarify (Tier 0, REQUIRED FIRST):
Restate scope of what is being executed — the selected plan file path and phase name. Under /goal autonomous execution: emit a 1-sentence restatement as an audit log entry and auto-proceed. Never skip the emit under /goal — it proves Tier-0 ran.
[E-S1] vc-context-discovery — load active plan context files and feature folder artifacts. Invoke vc-context-discovery: load the relevant context group files from process/context/all-context.md routing table, plus test context via the process/context/tests/all-tests.md routing chain. Do not skip — context group files contain the current state of implementation and key patterns that override stale training knowledge.
[E-S2] vc-plan-discovery — find related plans via frontmatter (same feature full depth, other features active-only, general-plans active). Pass the feature name (if provided) or task domain. Covers same-feature plans at full depth (active/backlog/completed/reports/refs) and other-feature active plans plus general-plans active, both via frontmatter.
Context Envelope (canonical C-2 order): At session start, populate the 10-field Context Envelope in the EXACT canonical order documented in .claude/skills/vc-context-discovery/SKILL.md §Context Envelope: feature → phase → session-goal → branch → worktree → context-group → blast-radius-packages → active-plan → test-runner → validate-contract. The phase field is EXECUTE for this agent. The test-runner multi-runner value uses the pipe-delimited DISPLAY format (bun test | vitest) that the phase-loop workflow template expands into SEQUENTIAL test steps — never run a literal bun test | vitest shell pipe.
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.
- 2d ago First seen · 539 lines · 36 tokens per session scan B 2634c99e1f37
vc-execute-agent is an agent published in the GitHub repository withkynam/vibecode-pro-max-kit (1,112 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 8,107 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
maintainer-orchestrator-design
This document explains the thinking behind the deerflow-maintainer-orchestrator skill: what it is for, the boundaries that make it safe to run, and the principles that shape how it reviews. It is written for DeerFlow maintainers who run the skill, and for anyone in the community who wants to understand — or adapt …
AGENTS
Lead Agent (packages/harness/deerflow/agents/leadagent/agent.py).
delegation
A SubAgent is an ephemeral child run spawned by a parent agent that inherits the parent's identity by default: same agent alias, same SecurityPolicy, same memory allowlist, same configured model provider, same tool registry. Auditable as a child via a tracing span agent. .subagent. .
overview
Agents are the star of a ZeroClaw deployment. Everything else in this book, the providers, the channels, the security profiles, the skills, the memory, exists so that an agent can use it. This section is the showcase; the rest of the docs are the credits.