agentleFS
blitzhash360-webblitzhash360-web/blitzhash-cloudflare-production-skills/.cursor/rules/cloudflare-waf-rules.mdc

blitzhash-cloudflare-production-skills / rules

Cursor rule0 starsChanged 9 days agoMITView on GitHub

Create, list and delete Cloudflare WAF custom rules from safe templates (block .env/.git probes, block WordPress probes, challenge the admin area, challenge countries) or a custom Rules-language expression, with dry-run and confirmation. Use when the user asks to block bots, attacks, countries or paths, or protect an admin page.

  • Reads credentials

The file

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

8 rules. About 0 are common, 1 is distinctive, and 7 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.

  • 7

    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:

    Add from template: cf-skills waf add --template block-sensitive-files

    line 15
  3. Very specific:

    Prefer managed_challenge over block when real users could match (admin pages, countries).

    line 23
  4. Very specific:

    Do not add block-wordpress-probes to a WordPress site.

    line 24
  5. Very specific:

    Every write command is a dry run by default.

    line 32
  6. Very specific:

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

    line 33
  7. Distinctive:

    Never delete records or rules the user did not name.

    line 34
  8. Very specific:

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

    line 35

≈ “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-waf-rules.mdc
---
description: Create, list and delete Cloudflare WAF custom rules from safe templates (block .env/.git probes, block WordPress probes, challenge the admin area, challenge countries) or a custom Rules-language expression, with dry-run and confirmation. Use when the user asks to block bots, attacks, countries or paths, or protect an admin page.
alwaysApply: false
---
<!-- Generated from skills/cloudflare-waf-rules/SKILL.md by scripts/build-cursor-rules.mjs. Edit the skill, not this file. -->

# Cloudflare WAF custom rules

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`.

## Commands

- See templates: `cf-skills waf templates`
- List rules: `cf-skills waf list`
- Add from template: `cf-skills waf add --template block-sensitive-files`
- Admin area: `cf-skills waf add --template challenge-admin --path /admin`
- Countries you do not serve: `cf-skills waf add --template challenge-countries --countries XX,YY`
- Custom: `cf-skills waf add --expression "(http.request.uri.path contains \"/internal\")" --action block --description "Block /internal"`
- Delete: `cf-skills waf delete --rule-id <id from list>`

## Guidance

- Prefer `managed_challenge` over `block` when real users could match (admin pages, countries). Use `block` for paths no human should request (`/.env`, `/.git/`).
- Do not add `block-wordpress-probes` to a WordPress site.
- Rules are appended to the `http_request_firewall_custom` phase entry point ruleset (created on first use). A rule with the same description is never duplicated.
- Free plan: 5 custom rules and no regex `matches` operator. After adding, ask the user to watch Security > Events for false positives for a few days.
- Token: Zone Read + Zone WAF Edit.

## 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.