agentmods.dev

cloudflare-deployment

cloudflare-deployment is a skill for Claude Code, Codex from porcupine-md/jonggrang. It costs 20 tokens per session (663 once invoked), scanned A, original, MIT.

A deployment guide for putting applications on Cloudflare Pages or Workers. Cloudflare provides hosting and edge services for websites and backend code.

In plain words
What is it for?
It validates Cloudflare access, builds the project, checks Wrangler configuration, provisions needed resources, and deploys the result.
Why use it?
It organizes authentication, building, resource setup, and deployment checks so the application is prepared correctly before release.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 11repo 12d ago A scan 20 tokens original MIT

Good fit It validates Cloudflare access, builds the project, checks Wrangler configuration, provisions needed resources, and deploys the result.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/porcupine-md/jonggrang/cloudflare-deployment
View source ↗ porcupine-md/jonggrang jonggrang.dev
Install

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.

Any agent
npx skills add porcupine-md/jonggrang --skill cloudflare-deployment
Clone the repo
git clone --depth 1 https://github.com/porcupine-md/jonggrang

Made for: Claude Code, Codex.

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 cloudflare-deployment

README.md
[![agentmods](https://agentmods.dev/badge/skills/porcupine-md/jonggrang/cloudflare-deployment/github.svg)](https://agentmods.dev/skills/porcupine-md/jonggrang/cloudflare-deployment)
Your own site
<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/cloudflare-deployment"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/cloudflare-deployment/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for cloudflare-deployment

Your own site · 80×15
<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/cloudflare-deployment"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/cloudflare-deployment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 663 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00663
Opus 5 $0.00010 $0.00331
Sonnet 5 $0.00004 $0.00133
Haiku 4.5 $0.00002 $0.00066

Measured 9d ago against content hash 487c20be0b98, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

cloudflare-deployment scanned grade A with 1 finding 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 9d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

3. Use `curl -sSf <URL>` to ensure the application returns a 200 OK status code. If it fails, use `npx wrangler tail` to inspect logs.
skills/library/deploy/cloudflare-deployment/SKILL.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Context

Deploying {{project_name}} ({{project_type}}) to Cloudflare (Pages or Workers). You will follow a strict 6-phase Deployment Lifecycle Contract.

Instructions

Execute the following phases in order:

Phase 1: Authentication

  1. Ensure the CLOUDFLARE_API_TOKEN environment variable is set to a valid Cloudflare API Token.
  2. If running locally, you may authenticate interactively with npx wrangler login. However, for automated agents, ensure the token is provided.
  3. Validate by running npx wrangler whoami.

Phase 2: Build

  1. Prepare the artifacts for deployment.
  2. If Cloudflare Pages (Frontend): Run your framework's build command (e.g., npm run build or yarn build) to generate the output directory (e.g., dist/ or out/).
  3. If Cloudflare Workers (Backend/Edge API): Run npm run build if your project requires transpilation (e.g., TypeScript). Wrangler may handle this automatically if configured.

Phase 3: Install / Provisioning

  1. Ensure the target Cloudflare resources exist.
  2. Check for wrangler.toml (for Workers) or wrangler.json (for modern Workers). Ensure the name field matches the intended project name.
  3. If it's a new project, ensure the necessary Cloudflare resources (KV namespaces, D1 databases, R2 buckets) are declared and provisioned if required.

Phase 4: Deploy

  1. Ship the artifact to Cloudflare.
  2. Cloudflare Pages: Run npx wrangler pages deploy <output-directory> --project-name <PROJECT_NAME>.
  3. Cloudflare Workers: Run npx wrangler deploy.

Phase 5: Checking

  1. Verify the deployment was successful.
  2. After a successful deploy, Wrangler outputs a URL (e.g., https://<PROJECT_NAME>.pages.dev or https://<WORKER_NAME>.<SUBDOMAIN>.workers.dev).
  3. Use curl -sSf <URL> to ensure the application returns a 200 OK status code. If it fails, use npx wrangler tail to inspect logs.

Phase 6: Update / Rollback

  1. If Phase 5 fails, immediately initiate a rollback.
  2. Cloudflare Workers: Rollback using npx wrangler rollback <VERSION_ID>. You can find versions using npx wrangler deployments list.
  3. Cloudflare Pages: Re-deploy the previous commit hash by finding the deployment ID in the Cloudflare dashboard or checking git history and re-running the deploy command on that commit.
  4. Note the failure in the progress log.

Read the full file on GitHub · 54 lines

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. 9d ago First seen · 54 lines · 20 tokens per session scan A 487c20be0b98

Subscribe to this mod's changes

cloudflare-deployment is a skill published in the GitHub repository porcupine-md/jonggrang (11 stars, last pushed 12d ago), licensed MIT. It adds 20 tokens to every session and 663 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

CloudDevOps and cloud
Related

Other skills, from other repositories

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…

google/skills · 83 tokens

gke-reliability

Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).

google/skills · 73 tokens

gke-workload-security

Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…

google/skills · 181 tokens

nemo-automodel-launcher-config

Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.

NVIDIA/skills · 30 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

cloud-architect

Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…

Jeffallan/claude-skills · 71 tokens