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/nimbus/claude-mdgit clone --depth 1 https://github.com/cloudflare/nimbusWrote 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/cloudflare/nimbus/claude-md)<a href="https://agentmods.dev/instructions/cloudflare/nimbus/claude-md"><img src="https://agentmods.dev/badge/instructions/cloudflare/nimbus/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 | $0.03540 | $0.03540 |
| Opus 5 | $0.01770 | $0.01770 |
| Sonnet 5 | $0.00708 | $0.00708 |
| Haiku 4.5 | $0.00354 | $0.00354 |
Grade A, and why
nimbus CLAUDE.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 4d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nimbus — agent context
Read this first if you're an AI agent picking up work on the Nimbus codebase. Sister file
CLAUDE.mdmirrors this content — keep them in sync.
What this project is
Nimbus builds documentation sites on Astro. The architecture splits into three tiers:
- User-owned starter files — visible UI components, layouts, and styling. Copied into the user's repo by
create-nimbus-docsand edited freely from then on. nimbus-docsnpm package — invisible plumbing (data helpers, validation, integration wiring, behavior primitives). Imported, not forked.- Registry — optional components, utilities, and agent-handoff features installed on demand via
nimbus-docs add <slug>.
Cloudflare is a first-class deploy target (the scaffolder defaults to it and ships wrangler.jsonc), but the framework is deploy-target agnostic — static output runs anywhere.
Repo layout
monorepo/
├── packages/
│ ├── nimbus-docs/ framework — integration, helpers, schemas, types, `nimbus` CLI
│ ├── nimbus-starter-source/ canonical source — fat tree; doubles as kitchen-sink dev app
│ │ ├── src/ components, layouts, pages, demo content
│ │ ├── templates/ per-variant content overrides (empty/, …)
│ │ └── starter.manifest.mjs declarative generation policy (registry-only slugs, dev-only paths, variants)
│ └── create-nimbus-docs/ scaffolder (`npx @cloudflare/create-nimbus-docs`) — CLI only, no templates
│ └── scripts/copy-template.mjs generator: canonical source + manifest → variant dirs (--out)
├── apps/
│ └── www/ docs site + registry hosting
│ └── registry/ manifests.ts (source), components/, features/, registry.json
├── examples/
│ └── local/ local sandbox (not drift-mirrored)
├── scripts/
│ ├── release.mjs release orchestration (detect → generate → verify → sync+tag → publish)
│ ├── sync-templates-repo.mjs sync generator output to the orphan templates branch + tag templates-v<version> (idempotent)
│ ├── templates-check.mjs PR CI: generate + scaffold + build
│ ├── check-no-major.mjs / freshness-guard.mjs release guards
│ ├── local.mjs / local-add.mjs local sandbox helpers
├── .generated/ gitignored generator output (templates); scratch for local/CI/release
├── pnpm-workspace.yaml
└── tsconfig.base.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.
- 4d ago First seen · 177 lines · 3,540 tokens per session scan A c2e4fd2f8bb0
nimbus CLAUDE.md is an instructions file published in the GitHub repository cloudflare/nimbus (947 stars, last pushed 5d ago), licensed MIT. It adds 3,540 tokens to every session, about $0.0177 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
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.