ViralForge
Agent-native viral video studio: one-click replicate viral short videos, deconstruct video hooks and scripts into a Viral DNA report, and ship 10 costed variants. Skill + MCP + CLI. Apache-2.0.
Runssource: GitHubTypeScriptApache-2.0commit cf08c8c87b04
TypeScript, Apache-2.0 licensed. The project labels itself: ai agent, ai agents, short video, short video generator, video editing, video script deconstruction, viral video and viral video generator.
ViralForge runs. An Argusic agent installed it in 12 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install, npm run build, and all 4 test suites (readme, smoke/e2e, media, mcp) pass with 0 failures. The dev server and preview server serve the studio UI. The CLI, MCP server, Playwright E2E tests, and media analysis all function without external API keys.
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.
- MCP server analyze_video tool failed: python3 couldn't import cv2 (opencv-python-headless not installed in system python due to PEP 668)3 minutes
- Node.js 18.19.1 installed but engine requires >=22.152 minutes
- MCP test expected shotCount: 5 but analyze.py returns 4 for glow.mp41 minute
- Playwright system deps failed to install (no root, su auth failure)
- Install time
- 12 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npm run test:all exited 0: 31/31 README checks, 23/23 smoke tests, 18/18 media checks, 5/5 MCP checks passed. Dev server at localhost:5173 returns 200. Preview server returns 200. CLI works. All 6 demo MP4s pass ffmpeg validation.
- Model tokens used
- 132,158
- Exact commit tested
- cf08c8c87b04
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/bin/sh -lc 'export NVM_DIR="$HOME/.nvm" && [ -s "$NVM_DIR/nvm.sh" ] && '"\\. \""'$NVM_DIR/nvm.sh" …
sleep 2
curl -s -o /dev/null -w '"'%{http_code}' http://127.0.0.1:4173/
echo \"\"
kill %1 2>/dev/null || true" in /work/repo
succeeded in 1969ms:
➜ Local: http://127.0.0.1:4173/
200
Everything works. Let me compile the final report.
tokens used
132,158
Everything works. Let me compile the final report.Replay 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.
- Recovered from all 4 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 12 minutes to install, slower than the median of the 78 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 79 ai-agent projects Argusic has installed and timed, ViralForge was the 55th fastest to reach a running state, and 54 of 79 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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)
ai-agentai-agentsshort-videoshort-video-generatorvideo-editingvideo-script-deconstructionviral-videoviral-video-generator
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/viralforge)Questions
- Does ViralForge run?
- Yes. ViralForge runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test ViralForge?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cf08c8c87b04. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test ViralForge?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ViralForge take to install?
- 12 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 ViralForge need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ViralForge?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does ViralForge compare with the alternatives?
- Of the 79 ai-agent projects Argusic has installed and timed, ViralForge was the 55th fastest to reach a running state, and 54 of 79 reached one at all.
- Where is the evidence for ViralForge?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.