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 instructions/dr-solodev/clawforge/agents-mdgit clone --depth 1 https://github.com/Dr-SoloDev/clawforgeWhat 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.00869 | $0.00869 |
| Opus 5 | $0.00434 | $0.00434 |
| Sonnet 5 | $0.00174 | $0.00174 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
clawforge AGENTS.md 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 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.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClawForge
Demo videos as code — YAML script → Playwright recording → edge-tts narration → ffmpeg → MP4.
Commands
npm test # Run all tests (node --test test/*.test.js)
npm start # node bin/clawforge.js
npm run example # Run examples/demo-script.yaml
clawforge check-deps # Verify ffmpeg, ffprobe, edge-tts, Playwright
clawforge validate <script.yaml> # Validate only, no execution
clawforge resume <checkpoint.json># Resume from .clawforge-checkpoints/
clawforge -o <dir> # Override output directory
clawforge --verbose # Verbose logging
External deps
ffmpeg+ffprobein PATHedge-ttsPython package (pip install edge-tts)- Chromium (
npx playwright install chromium)
Entrypoints
| Purpose | File |
|---|---|
| CLI | bin/clawforge.js |
| MCP stdio server | bin/clawforge-mcp.js |
| MCP SSE server (port 3100) | clawforge-mcp-sse/index.js |
| Library (npm package) | src/sdk-exports.js → exports ClawForgeSDK |
Architecture
ClawForgeSDK (events + checkpoint)
→ ProductionSession.run()
→ 1. narrate() edge-tts → per-scene MP3s
→ 2. record() Playwright → single MP4
→ 3. compose() ffmpeg → final MP4 (concat audio, mix music, burn subtitles/overlay)
MCP tools
clawforge_produce_video— script path or object, returns{outputPath, stats}clawforge_validate_script— validate without runningclawforge_check_dependencies— status of all depsclawforge_dry_run— validate + dep check
Two transports: stdio (npx clawforge-mcp) and SSE (GET /mcp, POST /mcp?sessionId=... on port 3100).
Tests
Uses Node.js built-in test runner. Files: test/smoke.test.js, validator.test.js, errors.test.js, subtitles.test.js, music.test.js, webcam.test.js.
CI (.github/workflows/ci.yml) tests on Node 20.x + 22.x, runs all tests + pipe JSON-RPC through MCP stdio server.
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 · 87 lines · 869 tokens per session scan A 7917e03bd04a
clawforge AGENTS.md is an instructions file published in the GitHub repository Dr-SoloDev/clawforge (11 stars, last pushed 1mo ago), licensed MIT. It adds 869 tokens to every session, about $0.0043 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 instructions, from other repositories
Browser4 CLAUDE.md
Instructions for platonai/Browser4, covering browser4 — project context for claude, architecture, key dispatch chain (cli → browser), batch commands and e2e test structure.
spring-ai-agentcore AGENTS.md
Instructions for spring-ai-community/spring-ai-agentcore, covering agents.md, project overview, architecture, key components and artifact store classes.
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
metamask-extension AGENTS.md
AGENTS.md instructions for MetaMask/metamask-extension, covering agents.md, agent instructions summary, critical rules for agents, comprehensive guidelines location and quick setup.
deckforge AGENTS.md
Instructions for tph-kds/deckforge, covering deckforge agent entry point, code intelligence, read order, default routing and non-negotiable implementation rules.
fast-browser CLAUDE.md
Claude Code instructions for m4ttstack/fast-browser, covering fast browser plugin, where a change belongs, fork branch: use fast-browser-runtime, releasing a new runtime and re-pinning this repo: use the script.