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 skills/abhiigatty/cld-flare-maxxing/source-command-cf-refreshnpx skills add AbhiiGatty/cld-flare-maxxing --skill source-command-cf-refreshgit 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/source-command-cf-refresh)<a href="https://agentmods.dev/skills/abhiigatty/cld-flare-maxxing/source-command-cf-refresh"><img src="https://agentmods.dev/badge/skills/abhiigatty/cld-flare-maxxing/source-command-cf-refresh.svg" alt="Measured on agentmods" 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.00026 | $0.00166 |
| Opus 5 | $0.00013 | $0.00083 |
| Sonnet 5 | $0.00005 | $0.00033 |
| Haiku 4.5 | $0.00003 | $0.00017 |
Grade A, and why
source-command-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 6d 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.
What it actually says
source-command-cf-refresh
Use this skill when the user asks to run the migrated source command cf-refresh.
Command Template
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.
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.
- 6d ago First seen · 21 lines · 26 tokens per session scan A 9755ec071a60
source-command-cf-refresh is a skill published in the GitHub repository AbhiiGatty/cld-flare-maxxing (2 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 166 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.
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”.
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…
cloudflare-workers-mcp
Software Development MCP server by Cloudflare.
workers-best-practices
Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from…