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/cloudflare/vibesdk/agents-mdgit clone --depth 1 https://github.com/cloudflare/vibesdkWhat 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.01600 | $0.01600 |
| Opus 5 | $0.00800 | $0.00800 |
| Sonnet 5 | $0.00320 | $0.00320 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
vibesdk 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Tooling
- Use Bun from the repository root. The tracked lockfile is
bun.lock, thespaceworkspace dependency usesworkspace:*, and install/build hooks invoke Bun even when started through npm. bun run setupis the interactive Cloudflare/resource bootstrap. Local development expects the generated.dev.vars; never commit.dev.vars*or.prod.vars.bun run devstarts the React frontend and Worker together through@cloudflare/vite-pluginathttp://localhost:5173. There is no separate Worker dev command.bun run dev:browseris an optional local Chromium sidecar for the think agent's browser-console tool; absence only produces a warning.
Verification
- Root checks:
bun run typecheck,bun run lint,bun run test,bun run build. bun run buildbuildsspaceand the Vite/Worker bundle; it does not typecheck. Runbun run typecheckseparately.- Focus a root test with
bunx vitest run path/to/file.test.ts; test execution uses the Workers pool andwrangler.test.jsonc. - The root Vitest suite excludes all
sdk/test/**andcontainer/monitor-cli.test.ts. SDK tests use Bun:bun run --cwd sdk test. - SDK integration tests require a running root dev server and
VIBESDK_INTEGRATION_API_KEY; runbun run --cwd sdk test:integration. They can take 5-10 minutes;VIBESDK_INTEGRATION_RUN_PREVIEW=1enables the slower preview case. - Root typecheck/lint do not validate
spaceorsdk. For touched packages runbun run --cwd space typecheck/bun run --cwd space buildandbun run --cwd sdk packageas appropriate. - ESLint checks only
src/**andworker/**and deliberately ignores tests; do not treatbun run lintas repository-wide validation. - Pre-commit typechecks staged TypeScript and runs related Vitest tests.
RUN_ALL_TESTS=1selects its broader suite;SKIP_TESTS=1bypasses the hook.
Frontend UI
- Tailwind CSS v4 via CSS-first setup in
src/index.css(@import 'tailwindcss',@theme, Kumo tokens); notailwind.config.*. - Prefer
@cloudflare/kumofor new UI. List components withbun kumo ls; component docs viabun kumo doc Button(swap name as needed). Legacy shadcn/Radix undersrc/components/ui/still exists—do not add new primitives there when Kumo covers the case. - Icons:
@phosphor-icons/react. Dark mode isdata-mode="dark"on the root (not aclassstrategy). - Path aliases:
@/*→src/*,shared/*,worker/*(seetsconfig.app.json).
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 · 55 lines · 1,600 tokens per session scan A d2ccf206b10b
vibesdk AGENTS.md is an instructions file published in the GitHub repository cloudflare/vibesdk (5,343 stars, last pushed 2d ago), licensed MIT. It adds 1,600 tokens to every session, about $0.0080 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
sark AGENTS.md
AGENTS.md instructions for Arjia-Labs/sark, covering agents.md — deploying sark, rules, phase 0 — prerequisites, phase 1 — clone and verify the tree and phase 2 — box credentials.
munkel CLAUDE.md
Instructions for limehq/munkel, covering claude.md, monorepo layout, commands, macos development specifics and deploy.
cloudbox AGENTS.md
Instructions for acoyfellow/cloudbox, covering cloudbox agent guide, canonical commands, deploy model, cloudflare account boundaries and required production secrets.
ctxlayer CLAUDE.md
Instructions for stevenn/ctxlayer, covering ctxlayer — claude code briefing, what runs where, architecture pointers, how a claude session should work in this repo and conventions.
sdl-mcp AGENTS.md
AGENTS.md instructions for GlitterKill/sdl-mcp, covering agents.md - sdl-mcp knowledge base, structure, where to look, architecture and conventions.
ctxlayer AGENTS.md
Instructions for stevenn/ctxlayer, covering working in this repo as an agent, golden path for any change, where things live, module rules and adding an endpoint.