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/tarekkharsa/agentstack/wrangler-cheatsheetnpx skills add Tarekkharsa/agentstack --skill wrangler-cheatsheetgit clone --depth 1 https://github.com/Tarekkharsa/agentstackWrote 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/tarekkharsa/agentstack/wrangler-cheatsheet)<a href="https://agentmods.dev/skills/tarekkharsa/agentstack/wrangler-cheatsheet"><img src="https://agentmods.dev/badge/skills/tarekkharsa/agentstack/wrangler-cheatsheet.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 | $0.00043 | $0.00696 |
| Opus 5 | $0.00022 | $0.00348 |
| Sonnet 5 | $0.00009 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
cloudflare_wrangler_cheatsheet 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 5d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrangler & Cloudflare surface cheatsheet
Unofficial, agentstack-authored. Not affiliated with or endorsed by Cloudflare.
Use this skill to pick the right wrangler command for a Cloudflare task without
guessing. Commands assume Wrangler v3+; run wrangler --version if unsure.
Workers
- Develop locally:
wrangler dev(add--remoteto run against the edge). - Deploy:
wrangler deploy(scope with--env <name>). - Validate a build only:
wrangler deploy --dry-run --outdir dist. - Live logs:
wrangler tail. - Roll back:
wrangler deployments list, thenwrangler rollback <id>.
Secrets & vars
- Set a secret:
wrangler secret put <NAME>(value entered interactively). - List secrets:
wrangler secret list. Delete:wrangler secret delete <NAME>. - Plaintext config vars live in
[vars]inwrangler.toml— never secrets.
KV (key-value)
- Create namespace:
wrangler kv namespace create <BINDING>. - Write/read:
wrangler kv key put <KEY> <VALUE> --binding <BINDING>/wrangler kv key get <KEY> --binding <BINDING>.
R2 (object storage)
- Create bucket:
wrangler r2 bucket create <NAME>. - Upload/download:
wrangler r2 object put <BUCKET>/<KEY> --file <PATH>/wrangler r2 object get <BUCKET>/<KEY>.
D1 (SQL)
- Create db:
wrangler d1 create <NAME>. - Run SQL:
wrangler d1 execute <NAME> --command "SELECT 1"or--file ./schema.sql. Use--localfor the local dev database.
Pages
- Deploy a build output dir:
wrangler pages deploy <DIST_DIR> --project-name <NAME>. - List projects/deployments:
wrangler pages project list/wrangler pages deployment list --project-name <NAME>.
DNS & zones
- DNS records are managed via the dashboard, API, or Terraform —
wranglerdoes not edit DNS. Use the Cloudflare MCP or API to read zone and record state, and treat record changes as reviewed infrastructure changes, not ad-hoc edits.
Conventions
- Match the binding name in
wrangler.tomlto the variable name your code reads fromenvso config and runtime stay in sync. - Use
--localfor D1/KV during development to avoid mutating production data.
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.
- 5d ago First seen · 69 lines · 43 tokens per session scan A 56fafc6be113
cloudflare_wrangler_cheatsheet is a skill published in the GitHub repository Tarekkharsa/agentstack (3 stars, last pushed 22d ago), licensed Apache-2.0. It adds 43 tokens to every session and 696 once invoked, about $0.0002 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
infra-sync
Keep Terraform and CDK infrastructure in sync. Compares terraform/aws-ecs/ and infra/ to identify discrepancies in ECS services, networking, storage, secrets, IAM, and configuration. Reports parity gaps and generates fixes for the target IaC tool. Use when changes are made to either Terraform or CDK infrastructure.
mcp-runtime-platform-public
Configure and debug public MCP Runtime installs with MCPPLATFORMDOMAIN, Let's Encrypt, registry/mcp/platform hostnames, registry TLS auth, and platform UI ingress. Use for --with-tls setup, ACME failures, DNS NXDOMAIN, registry forward-auth, or production hostname routing — not for local Kind test-mode (use…
mcp-runtime-troubleshooting
Debug MCP Runtime cluster, ingress, registry, Sentinel auth, MCPServer pods, and platform UI failures on Kind or k3s. Use when setup, doctor, e2e, or live traffic fails; when investigating 401/404/ImagePullBackOff/ACME/TLS/registry push errors; or when AGENTS.md points here for the full failure-mode checklist.
terraform-setup
Install (deploy) MCP Gateway & Registry on AWS using the Terraform aws-ecs stack (ECS Fargate, Aurora, DocumentDB, Keycloak). Asks whether you are running from an EC2 instance or a local laptop, confirms the required AWS IAM permissions are in place, clones the repository, bootstraps the toolchain (uv, AWS CLI…
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
application-design-center-design-deploy
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting…