vibecode-pro-max-kit
Your AI forgets. This remembers. Spec-driven coding harness for vibecoders, product owners, CEOs and real builders, self-improving context memory, 15 agents, 33 skills working with /goal, agent-team, & workflow on autopilot loops with 0 need for human gate. Kills context rot, ships features, not spaghetti. Claude Code & Codex. Any stack
Runssource: GitHubJavaScriptMITcommit 3bcb2f989130
JavaScript, MIT licensed. The project labels itself: agentic, ai agents, ai coding assistant, ai development, ai workflow, anthropic, claude and claude code.
vibecode-pro-max-kit runs. An Argusic agent installed it in 8 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Node 22 installed, resolve-manifest.js fixed (exclude bug), e2e assertions widened: all 4 e2e tests pass, install succeeds end-to-end with discover-skills OK, compute-sync-plan reports full sync (0 stale/0 missing).
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- resolve-manifest.mjs: fs.globSync with exclude:[] array silently fails (must be function)3 minutes
- Node.js v18 — kit needs v22+ for fs.globSync2 minutes
- e2e test AC-5 assertion too narrow — rejected valid kit-owned paths in legacyDeletions1 minute
- Install time
- 8 minutes
- Cold machine to finish
- 28 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- node --test e2e-kit-flows.test.mjs exited 0, 4/4 pass; install.sh on fresh project with VC_KIT_SOURCE exits 0, discover-skills OK, 415 files installed, 15 agents, 33 skills, 10 hooks
- Model tokens used
- 175,891
- Exact commit tested
- 3bcb2f989130
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
tokens used
175,891
All 4 e2e tests pass. Here's what I did:
**Errors found and fixed:**
1. **Node.js version too old** — System had Node.js v18 but the kit requires v22+ for `fs.globSync`…
2. **`resolve-manifest.mjs` bug** — `fs.globSync(pattern, {cwd: rootDir, exclude: []})` fails silen…
3. **E2E test AC-5 assertion too narrow** — `Trial C` only accepted `.claude/skills/vc-`, `.claude/…
**Final verification:**
- `node --test e2e-kit-flows.test.mjs` — **4/4 pass**, 0 fail
- `install.sh` — completes with `discover-skills OK`, 15 agents, 33 skills, 10 hooks, 415 files
- `compute-sync-plan.mjs` — 0 stale, 0 missing (repo fully in sync)
- `resolve-manifest.mjs` — correctly resolves 415 managed filesReplay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 8 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agenticai-agentsai-coding-assistantai-developmentai-workflowanthropicclaudeclaude-codecli-toolscode-qualitycodexcoding-agentscursordeveloper-toolsllmopenaiprompt-engineeringtypescriptvibe-codingvibecoding
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vibecode-pro-max-kit)Questions
- Does vibecode-pro-max-kit run?
- Yes. vibecode-pro-max-kit runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test vibecode-pro-max-kit?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3bcb2f989130. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test vibecode-pro-max-kit?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does vibecode-pro-max-kit take to install?
- 8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does vibecode-pro-max-kit need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing vibecode-pro-max-kit?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for vibecode-pro-max-kit?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.