agentleFS
Sign inStart free
blitzhash360-webblitzhash360-web/blitzhash-cloudflare-production-skills/.cursor/rules/cloudflare-zone-audit.mdc

blitzhash-cloudflare-production-skills / rules

Cursor rule0 starsChanged 9 days agoMITView on GitHub

Read-only security posture audit of a Cloudflare zone (SSL mode, HTTPS, TLS, WAF, rate limiting, bots, DNSSEC, exposed origin IPs, dangling CNAMEs) with plain-English findings and a score out of 100. Use when the user asks if their Cloudflare setup or domain is secure, launch-ready, or what to fix first.

  • Reads credentials

The file

We split this cloudflare-zone-audit.mdc into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run commands with npx -y github:blitzhash360-web/blitzhash-cloudflare-production-skills <command> or, inside a clone of the repo, node …

    line 9
  2. Very specific:

    Run cf-skills audit --zone <domain>.

    line 18
  3. Very specific:

    Every write command is a dry run by default.

    line 33
  4. Very specific:

    Only after that "yes", re-run the same command with --apply --yes (your shell is not interactive).

    line 34
  5. Distinctive:

    Never delete records or rules the user did not name.

    line 35
  6. Very specific:

    Run cf-skills audit before and after changes and tell the user what moved.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
cloudflare-zone-audit.mdc
---
description: Read-only security posture audit of a Cloudflare zone (SSL mode, HTTPS, TLS, WAF, rate limiting, bots, DNSSEC, exposed origin IPs, dangling CNAMEs) with plain-English findings and a score out of 100. Use when the user asks if their Cloudflare setup or domain is secure, launch-ready, or what to fix first.
alwaysApply: false
---
<!-- Generated from skills/cloudflare-zone-audit/SKILL.md by scripts/build-cursor-rules.mjs. Edit the skill, not this file. -->

# Cloudflare zone audit

Run commands with `npx -y github:blitzhash360-web/blitzhash-cloudflare-production-skills <command>` or, inside a clone of the repo, `node bin/cf-skills.mjs <command>`. Below, `cf-skills` means either. Zone is `--zone <domain or zone id>` or `$CLOUDFLARE_ZONE_ID`.

## When to use

The user wants to know how well their domain is protected, or before/after any Cloudflare change.

## Steps

1. Confirm `CLOUDFLARE_API_TOKEN` is set (`cf-skills verify-token`). If not, point the user to `docs/TOKEN-PERMISSIONS.md` (read-only audit token).
2. Run `cf-skills audit --zone <domain>`. It only makes GET requests.
3. Summarise for a non-technical founder: score, then each FAIL in one sentence (what it means for their customers), then the fix.
4. Offer the matching fix commands as dry runs (they change nothing):
   - WAF missing: `cf-skills waf add --template block-sensitive-files`
   - Rate limiting missing: `cf-skills ratelimit add --template protect-login`
   - Origin IP exposed: `cf-skills dns update --name <n> --type A --proxied true` (check it is a web record, not mail)
   - Dangling CNAME: `cf-skills dns delete --name <n> --type CNAME` (only after the user confirms it is unused)
   - SSL / HTTPS / TLS / Bot Fight Mode / DNSSEC: explain the dashboard toggle; these scripts do not change zone settings.
5. For CI, `cf-skills audit --fail-under 70` exits with code 3 when the score is lower.

A SKIP line means the token lacks a read permission; that check is left out of the score.

## Safety rules (always)

- The API token lives only in the environment (`CLOUDFLARE_API_TOKEN`) or a git-ignored `.env`. Never ask the user to paste it into chat, never print it, never pass it as a flag, never commit it.
- Every write command is a **dry run** by default. Run it without `--apply` first, show the user the printed plan, and wait for an explicit "yes" in chat.
- Only after that "yes", re-run the **same** command with `--apply --yes` (your shell is not interactive). Never add `--yes` on your own initiative.
- Never delete records or rules the user did not name. Never widen the token's permissions.
- Run `cf-skills audit` before and after changes and tell the user what moved.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free