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/skills/vc-review-situation/SKILL.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/skills/withkynam/vibecode-pro-max-kit/vc-review-situation)<a href="https://agentmods.dev/skills/withkynam/vibecode-pro-max-kit/vc-review-situation"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-review-situation/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/skills/withkynam/vibecode-pro-max-kit/vc-review-situation"><img src="https://agentmods.dev/badge/skills/withkynam/vibecode-pro-max-kit/vc-review-situation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.02063 |
| Opus 5 | $0.00022 | $0.01032 |
| Sonnet 5 | $0.00009 | $0.00413 |
| Haiku 4.5 | $0.00004 | $0.00206 |
Grade A, and why
vc-review-situation 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 9d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Situation
Output style: lead with the bottom line, bullets over prose, one-line TL;DR —
process/development-protocols/communication-standards.md.
Summarize the current repo state for handoff and resume work.
This is a helper skill only.
- Do use it for read-only branch, worktree, and active-plan summaries.
- Do use it to surface likely selected-plan context when it can be proven or safely hinted.
- Do not use it to choose a plan authoritatively.
- Do not use it to approve execution, resume execution, or mutate repo/process state.
Mode Selection
vc-review-situation operates in two modes. Choose based on the trigger signals below.
Simple Mode (default)
Run review-situation-scan.cjs, return the scan summary.
Use when:
- User asks "what's in flight", "what's next", "give me a handoff summary"
- Quick orientation needed at the start of a session
- Orchestrator needs a branch/plan status check before routing
Output: Current State, Recent Work, In-Flight Plans, Next Steps, Warnings (standard scan sections).
Deep Mode
Run the scan plus read umbrella plan, latest phase report, and all active-plan handoff sections. Synthesize into a full handoff briefing sufficient for an agent to resume without follow-up questions.
Trigger conditions (any one):
- User asks for a full program review: "what are we building", "summarize all active plans", "where are we in the program"
- Session is resuming after a long break or context compaction occurred
- Orchestrator needs a thorough handoff before routing to a phase agent
- Caller explicitly requests deep mode
- Program Review Mode is active — Program Review Mode is Deep Mode
Deep mode steps:
- Run
review-situation-scan.cjsas normal (get branch state + active plan list) - If a phase program is active: read the umbrella plan in full — especially
## Current Execution Stateand## Phase Ordering - Read the most recent phase report in full (if it exists)
- If 3+ phases are completed: read the Forward Preview sections from earlier phase reports
- For each active plan: read the
## Resume and Execution Handoffsection - Synthesize: "You are at Phase N of M. Phase N-1 completed with these outputs. The next phase needs to know: X. These are the open gaps from prior phases: Y."
What ships with it
3 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.
- 9d ago First seen · 189 lines · 44 tokens per session scan A c79e0fae4414
vc-review-situation is a skill published in the GitHub repository withkynam/vibecode-pro-max-kit (1,118 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 2,063 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
gh-pr
Create, review, or manage GitHub pull requests. Use when asked to open, check, or merge a PR.
branch
Create or switch to a feature branch, typically tied to a GitHub issue. Use when asked to create a branch or start work on an issue.
changelog
Generate a changelog or release notes from recent git history. Use when asked to write a changelog, summarize recent commits, or produce release notes.
commit
Draft and create a git commit for staged changes. Use when asked to commit.
contribute-spec-fix
Fix a broken OpenAPI spec in jentic-public-apis with an OpenAPI Overlay, validate it (spectral lint + idempotency check), and contribute it back via a PR to the community catalog. Falls back to applying the same overlay to the local Jentic registry if the user can't wait for maintainer approval, and closes the loop by…
flame-harness-submit
Phase 10 — upload store text metadata + categories via fastlane, then pause with exact manual steps for the final iOS review submission and Android production promotion.