Borrowing it
Nothing to install: this file belongs to AbhiiGatty/cld-flare-maxxing. 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/AbhiiGatty/cld-flare-maxxing/main/.agents/skills/cloudflare-maxxing/SKILL.mdgit clone --depth 1 https://github.com/AbhiiGatty/cld-flare-maxxingWrote 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/skills/abhiigatty/cld-flare-maxxing/cloudflare-maxxing)<a href="https://agentmods.dev/skills/abhiigatty/cld-flare-maxxing/cloudflare-maxxing"><img src="https://agentmods.dev/badge/skills/abhiigatty/cld-flare-maxxing/cloudflare-maxxing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/abhiigatty/cld-flare-maxxing/cloudflare-maxxing"><img src="https://agentmods.dev/badge/skills/abhiigatty/cld-flare-maxxing/cloudflare-maxxing.svg" alt="Reviewed on agentmods" width="80" 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.00088 | $0.00590 |
| Opus 5 | $0.00044 | $0.00295 |
| Sonnet 5 | $0.00018 | $0.00118 |
| Haiku 4.5 | $0.00009 | $0.00059 |
Grade A, and why
cloudflare-maxxing 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 10d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare maxxing — teach + recommend
Goal: help the user understand the Cloudflare platform and use it to the maximum for their actual stack — not a generic feature dump, but grounded, prioritized, do-this-next guidance.
How to respond
- Ground in their real account first. Read
reports/latest-report.jsonand the latest snapshot (snapshots/<latest>/snapshot.jsonviasnapshots/index.json). If stale/missing, offernpm run refresh(read-only). Know what they already use before recommending. - Map need → primitive. Use use-cases.md: "I want to do X → use these Cloudflare products, wired this way, on this plan." Always name the smallest viable starting point.
- Know the whole surface. Use platform-map.md for the full product catalog grouped by domain, with maturity + free-tier notes — so you don't miss an option.
- Reach for the frontier. Check
reference/betas.json(already scored against their stack bynpm run betas) for beta/early-access features worth piloting. - Verify before asserting. Use the
cloudflare-docsMCP (search_cloudflare_documentation) for current syntax, limits, and availability. Cite the docs URL. Prefer current docs over memory.
Teaching style
- Lead with the "why" and the use case, then the product, then a concrete first step.
- Always state the free-tier position and any limit that matters (
reference/limits.json). - Distinguish quick wins (a config toggle / one rule) from projects (a new build).
- Give a runnable starting point: a
wranglerconfig sketch, a binding, or a docs quickstart link. - When relevant, hand off: deep account analysis →
cf-optimizeragent; "design my solution" →cf-architectagent; "what's my state / who changed X" →cf-investigatoragent.
Safety
Read-only by default. Never change the account from this skill. If a recommendation requires a
change, describe the guarded action + break-glass path (docs/SAFETY.md) and let the user run it.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 36 lines · 88 tokens per session scan A eae6cc8c7531
cloudflare-maxxing is a skill published in the GitHub repository AbhiiGatty/cld-flare-maxxing (2 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 590 once invoked, about $0.0004 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-31.
Other skills, from other repositories
prepare-cloudflare-production-deployment
Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment. Use when setting up or auditing Cloudflare MCP resources, wrangler.jsonc bindings, Worker secrets, Turnstile, Email Sending, GitHub Actions secrets/variables, or GitHub CLI deployment wiring for this…
hello-site
Reproduce a Davflare static site with existing MCP tools only (publishsite / imageupload). Use when onboarding or demoing “chat → site”.
cloudflare-workers-mcp
Software Development MCP server by Cloudflare.
review-configuration
Config, env, wrangler review. USE WHEN: user runs /review-configuration or explicitly asks for this review. DO NOT USE WHEN: implementing features or fixing bugs unless the user asked for a review.
review-wrangler
Wrangler/Workers config review (wrangler.jsonc files, compatibility dates, bindings, observability, generated types) against current official Cloudflare best practices. USE WHEN: user runs /review-wrangler or explicitly asks for this review. DO NOT USE WHEN: reviewing app code, other dev dependencies, or implementing…
wrangler
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over…