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/dmmulroy/cloudflare-skill/agents-mdgit clone --depth 1 https://github.com/dmmulroy/cloudflare-skillWhat 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.00637 | $0.00637 |
| Opus 5 | $0.00318 | $0.00318 |
| Sonnet 5 | $0.00127 | $0.00127 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
cloudflare-skill 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 3d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PROJECT KNOWLEDGE BASE
Generated: 2026-01-28
OVERVIEW
Documentation/skill repository for Cloudflare platform—structured reference docs for AI/LLM consumption. No executable code.
STRUCTURE
./
├── README.md # Project overview + install instructions
├── LICENSE # MIT license
├── install.sh # Installation script
├── command/
│ └── cloudflare.md # /cloudflare slash command
└── skills/
└── cloudflare/
├── SKILL.md # Main skill manifest + decision trees
└── references/ # Product subdirs
└── <product>/
├── README.md
├── api.md
├── configuration.md
├── patterns.md
└── gotchas.md
WHERE TO LOOK
| Task | Location | Notes |
|---|---|---|
| Find a product | skills/cloudflare/SKILL.md |
Decision trees + full index |
| Product reference | skills/cloudflare/references/<product>/ |
5-file structure |
CONVENTIONS
VCS: jujutsu (NOT git)
# CORRECT
jj status
jj log
jj new
jj commit -m "msg"
# WRONG - do not use
git status # .jj/ present = use jj
Reference File Structure
Every product follows 5-file pattern:
README.md— Overview, when to useapi.md— Runtime API referenceconfiguration.md—wrangler.toml+ binding setuppatterns.md— Usage patternsgotchas.md— Pitfalls, limitations
YAML Frontmatter
SKILL.md files use frontmatter for machine parsing:
---
name: product-name
description: Brief description
references:
- related-product
---
ANTI-PATTERNS
SQL Injection (D1)
// NEVER - string interpolation
const result = await db.prepare(`SELECT * FROM users WHERE id = ${id}`).all();
// ALWAYS - prepared statements with bind()
const result = await db.prepare("SELECT * FROM users WHERE id = ?").bind(id).all();
Secrets Management
# NEVER commit .dev.vars (contains secrets)
# NEVER hardcode secrets in code
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.
- 3d ago First seen · 116 lines · 637 tokens per session scan A 554dd656d52e
cloudflare-skill AGENTS.md is an instructions file published in the GitHub repository dmmulroy/cloudflare-skill (729 stars, last pushed 7mo ago), licensed MIT. It adds 637 tokens to every session, about $0.0032 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
apex-accelerator iac-bicep-best-practices.instructions.md
Bicep-specific IaC best practices for Azure templates. Security baseline, naming, AVM mandate, anti-patterns.
awsmux AGENTS.md
Instructions for 0hardik1/awsmux, covering agents.md, what awsmux is, build, test, verify, layout and the safety model — invariants you must not weaken.
terraform-provider-pipefy AGENTS.md
Instructions for pipefy/terraform-provider-pipefy, covering agents.md, project overview, setup and requirements, essential commands and project layout.
plan-forge azd.instructions.md
Azure Developer CLI (azd) patterns — azure.yaml structure, infra folder, tags, hooks, pipelines.
plan-forge terraform.instructions.md
Terraform Azure patterns — file structure, providers, state, naming, security, testing.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.