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-predictnpx skills add withkynam/vibecode-pro-max-kit --skill vc-predictgit 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-predict)<a href="https://agentmods.dev/skills/withkynam/vibecode-pro-max-kit/vc-predict"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-predict.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.00034 | $0.01890 |
| Opus 5 | $0.00017 | $0.00945 |
| Sonnet 5 | $0.00007 | $0.00378 |
| Haiku 4.5 | $0.00003 | $0.00189 |
Grade A, and why
vc-predict 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 4d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vc-predict — Multi-Persona Pre-Analysis
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Five expert personas independently analyze a proposed change, then debate conflicts to produce a consensus verdict before a single line of code is written.
When to Use
- Before implementing a major or high-risk feature
- Before a significant refactor or architecture change
- Evaluating competing technical approaches
- Stress-testing assumptions in a proposed design
When NOT to Use
- Trivial or low-risk changes (use
debuggerfor bugs,generate-plan/plan-agentfor already-decided tasks) - Already-approved work with no open design questions
- Pure dependency upgrades with no API changes
Mode Selection
vc-predict runs in Simple or Deep mode. Choose based on the conditions below.
| Simple | Deep | |
|---|---|---|
| Context source | Approach description already in context | Approach description + historical research subagent |
| Subagent spawned | No | Yes — reads git log, prior reports, test failure history |
| Persona debate quality | Reasons from first principles | "We tried this 3 months ago and hit X" |
| When to use | Contained feature, clear scope, no prior attempts | See trigger conditions below |
Deep Mode — Trigger Conditions (any one is sufficient)
- The approach involves a pattern previously attempted in this codebase (git history may show prior attempts)
- The approach touches a surface with known failure history: auth, billing, container lifecycle, streaming, or WebSocket reconnect
- Caller explicitly requests deep mode (
--deepflag or "use deep predict") - The plan is COMPLEX shape and this is the pre-checklist predict call
Simple Mode — Trigger Conditions (default)
- Approach is a contained feature with clear scope
- No prior attempts at this surface area are likely
- Plan is SIMPLE shape and the design is not controversial
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.
- 4d ago First seen · 185 lines · 34 tokens per session scan A c8b78a0bef17
vc-predict is a skill published in the GitHub repository withkynam/vibecode-pro-max-kit (1,115 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 1,890 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
implement
End-to-end workflow for taking MCP work items from backlog to merged PR. Handles git branching, schema-driven planning, implementation, independent review, and PR creation. Composes spec-quality, review-quality, and schema-workflow skills into a single pipeline. Use when a user says "implement this", "work on this…
session-retrospective
Analyzes the current implementation run — evaluates schema effectiveness, delegation alignment, note quality, and plan-to-execution fit. Captures cross-session trends and proposes improvements when patterns repeat. Use after implementation runs, or when user says 'retrospective', 'session review', 'what did we learn'…
ralph
Launcher for the Ralph-style queue drain script — emits the right node ralph-loop.mjs invocation based on the user's filter and bounds. The actual loop runs as a Node script that spawns one claude -p --worktree per iteration; this skill is the configurator, not the loop. Use when a user says: drain the backlog, ralph…
quick-start
Interactive onboarding for the MCP Task Orchestrator. Detects empty or populated workspaces and walks through how plan mode, persistent tracking, and the MCP work together. Use when a user says "get started", "how do I use this", "quick start", "first time setup", "onboard me", "what can this MCP do", or "help me…
review-proposals
Triages pending improvement-proposal MCP items — presents each with its scope and evidence, collects an accept/reject/defer decision per proposal, and carries out the disposition: project-scoped acceptances get their exact YAML applied to .taskorchestrator/config.yaml and pushed per-root; global acceptances get a…
adopt-project-scope
Migrates an already-populated, unscoped Task Orchestrator database in place to the project-scoping convention — creates a project anchor root, re-parents existing work trees under it, and writes rootId back to config.yaml. Use when a user says: adopt project scope, migrate this database to project scoping, make this…