Borrowing it
Nothing to install: this file belongs to luke-fairbanks/broll. 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/luke-fairbanks/broll/main/CLAUDE.mdgit clone --depth 1 https://github.com/luke-fairbanks/brollWrote 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/instructions/luke-fairbanks/broll/claude-md)<a href="https://agentmods.dev/instructions/luke-fairbanks/broll/claude-md"><img src="https://agentmods.dev/badge/instructions/luke-fairbanks/broll/claude-md.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.1 | $0.00778 | $0.00778 |
| Opus 5 | $0.00389 | $0.00389 |
| Sonnet 5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade C, and why
broll CLAUDE.md scanned grade C with 1 finding 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 8d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- npm sometimes drops rolldown/sharp native bindings (npm/cli#4828): fix is `rm -rf node_modules package-lock.json && npm install`. How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
broll — architecture rules
broll is an MCP server that gives coding agents content-production hands: BYO-key generation, deterministic rendering, draft-first publishing. These rules are binding for all changes.
Non-negotiables
- The model plans; code renders. Anything that must look consistent (layout, fonts, spacing, captions, branding) lives in TypeScript, never in a prompt. If AI output drifts, the fix is moving that part into code.
- Determinism.
compilePlanandslideOverlaySvgare pure functions: same inputs → same ffmpeg args / same SVG. NoDate.now(), no randomness in render paths. IDs come from the injectableIdGenerator. - Draft-first publishing. No code path may post to a network without (a) a draft file existing in the outbox and (b)
confirm: truefrom the caller. Never weaken this. - BYO keys only. Keys are read from env, sent only to their vendor's API, never logged, never proxied.
- Errors must be actionable. Every thrown error tells the agent what to do next (which tool to call, which env var to set). ffmpeg failures include the stderr tail.
Layout
src/config.ts— env +broll.config.json(brand kit). zod-validated.src/workspace.ts— on-disk state: assets/renders/drafts/tmp + manifest. All tool outputs are inspectable files.src/render/— the crown jewel.plan.tscompiles declarative RenderPlans to ffmpeg args (pure);renderer.tsis the only orchestrator;ffmpeg.tsis the only place a process spawns;carousel.tscomposes slides via sharp+SVG.src/providers/— Strategy pattern.registry.tspicks explicit → config default → first configured → mock. The mock provider must always keep every workflow runnable keyless.src/social/— Adapter pattern per platform +constraints.ts(validate before publish) +drafts.ts(outbox) +publisher.ts(per-platform results, never all-or-nothing).src/server.ts— thin MCP tool wrappers only; logic lives in services.src/broll.tsis the composition root.
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.
- 8d ago First seen · 34 lines · 778 tokens per session scan C 841e8f268430
broll CLAUDE.md is an instructions file published in the GitHub repository luke-fairbanks/broll (5 stars, last pushed 1mo ago), licensed MIT. It adds 778 tokens to every session, about $0.0039 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.