cld-flare-maxxing: Command for Claude Code

.claude/commands/cf-refresh.md

cf-refresh is a command for Claude Code from AbhiiGatty/cld-flare-maxxing. It costs 20 tokens per session (174 once invoked), scanned A, original, MIT.

A command that takes a fresh read-only inventory of a Cloudflare account and rebuilds its findings and dashboard data. Cloudflare provides services such as domain management, DNS, and website security.

In plain words
What is it for?
Use it to refresh Cloudflare data before investigating problems or reviewing account health. It summarizes resource counts, recommended fixes, limits near capacity, and audit-log activity.
Why use it?
It replaces possibly outdated account information with a current snapshot and identifies skipped checks, security findings, usage limits, and recent sensitive changes. It does not modify the account.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is AbhiiGatty/cld-flare-maxxing's own configuration. It tells Claude Code how to work on cld-flare-maxxing itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cld-flare-maxxing configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is Bash(npm run refresh:*), Bash(node scripts/snapshot.mjs:*), Bash(node scripts/report.mjs:*), Bash(node scripts/betas.mjs:*), Bash(node scripts/build-dashboard-d.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/AbhiiGatty/cld-flare-maxxing/main/.claude/commands/cf-refresh.md
Clone the repo
git clone --depth 1 https://github.com/AbhiiGatty/cld-flare-maxxing

Made for: Claude Code.

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

agentmods badge for cf-refresh

README.md
[![agentmods](https://agentmods.dev/badge/commands/abhiigatty/cld-flare-maxxing/cf-refresh.svg)](https://agentmods.dev/commands/abhiigatty/cld-flare-maxxing/cf-refresh)
Your own site
<a href="https://agentmods.dev/commands/abhiigatty/cld-flare-maxxing/cf-refresh"><img src="https://agentmods.dev/badge/commands/abhiigatty/cld-flare-maxxing/cf-refresh.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 174 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00174
Opus 5 $0.00010 $0.00087
Sonnet 5 $0.00004 $0.00035
Haiku 4.5 $0.00002 $0.00017

Measured 7d ago against content hash e6be1cd5ce9f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

cf-refresh 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 7d 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.

.claude/commands/cf-refresh.md · 15 lines

What it actually says

Run npm run refresh (snapshot → report → betas → dashboard data) using the read-only token.

Then summarize for me:

  • The counts (zones, DNS records, workers, etc.) and any collectors that were skipped (snapshot.errors).
  • The top critical/high findings with their recommended fixes.
  • Any plan limits at or above 80% utilization.
  • Notable recent sensitive changes from the audit log (who did what).

Do NOT make any changes to the account — this is read-only.

Changes

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.

  1. 7d ago First seen · 15 lines · 20 tokens per session scan A e6be1cd5ce9f

Subscribe to this mod's changes

cf-refresh is a command published in the GitHub repository AbhiiGatty/cld-flare-maxxing (2 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 174 once invoked, about $0.0001 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.