Borrowing it
Nothing to install: this file belongs to praveenjuge/teak. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/praveenjuge/teak/main/.agents/skills/wrangler/SKILL.mdgit clone --depth 1 https://github.com/praveenjuge/teakWrote 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/praveenjuge/teak/wrangler)<a href="https://agentmods.dev/skills/praveenjuge/teak/wrangler"><img src="https://agentmods.dev/badge/skills/praveenjuge/teak/wrangler/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.
<a href="https://agentmods.dev/skills/praveenjuge/teak/wrangler"><img src="https://agentmods.dev/badge/skills/praveenjuge/teak/wrangler.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.02232 |
| Opus 5.5 | $0.00024 | $0.00893 |
| Sonnet 5.5 | $0.00012 | $0.00446 |
| Haiku 4.5 | $0.00006 | $0.00223 |
Grade A, and why
wrangler 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 2d 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.
This is a copy
88% identical to wrangler — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrangler CLI
Use this skill only when the project has wrangler.jsonc, wrangler.json, or wrangler.toml and no cloudflare.config.ts, or when the user asks for Wrangler. For a new project, a project with cloudflare.config.ts, or a project with no Cloudflare configuration, use the Cloudflare CLI (cf) instead: load the cf-cli skill if it is installed, or follow Use cf with coding agents. Do not add Wrangler to those projects.
Use the project's Wrangler version and retrieve the relevant documentation before writing commands or configuration. CLI flags and configuration fields change; do not rely on memorized examples.
Inspect the Project
- Find the package manager, installed Wrangler version, package scripts, framework, and Wrangler config. Run commands through the project's scripts or package manager so they use its local version. Install dependencies using the existing lockfile when needed; do not silently upgrade Wrangler to match current docs. If the project has a Wrangler configuration file but Wrangler is not a dependency, follow the installation guide to add it locally.
- Identify the config used by the build or deploy command, including framework-generated config. Edit its source rather than generated output.
- Establish the target account, Worker, environment, and resource before running commands that change them. For data operations, determine whether the target is local or remote.
Retrieve What the Task Needs
Use the Cloudflare MCP docs tool if available, or fetch the relevant linked page directly. Follow links to the specific command or product involved; avoid loading the entire reference. If a page moves, rediscover it through the Wrangler command index or Cloudflare docs search.
| Task | Source |
|---|---|
| Discover commands and flags, including resource management, deployments, rollback, and diagnostics | Project-local wrangler --help and wrangler <command> --help; command reference |
| Edit config or add a binding | Installed wrangler/config-schema.json (usually under node_modules); configuration reference |
| Deploy a framework application | Framework guides; follow the guide for the project's existing framework and adapter |
| Migrate an application to Workers when requested | Pages to Workers; Vercel to Workers |
| Configure staging or production | Environments |
| Set secrets locally, in CI, or on a deployed Worker | Secrets |
| Generate binding and runtime types | TypeScript |
| Run locally or choose a testing approach | Local development; testing |
| Choose roles, scopes, or API token permissions for Wrangler | Roles and permissions; Workers roles and permissions |
| Create or manage a branch or pull request environment | Previews overview; get started; configuration |
| Decide whether Preview resources are isolated or shared | Resources and isolation, including its current limitations |
| Configure Preview URLs, access, debugging, or CI | Custom domains; test and debug; examples |
| Choose between Previews, Version URLs, and Wrangler environments | Compare workflows |
| Diagnose authentication or select an account | General commands, including whoami; authentication profiles |
| Deploy an unauthenticated prototype | Claim deployments for eligibility, expiry, and claim URL handling; use a permanent account for production or CI |
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.
- 2d ago First seen · 72 lines · 60 tokens per session scan A 7884f560509c
wrangler is a skill published in the GitHub repository praveenjuge/teak (25 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 2,232 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to wrangler, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
winui-wpf-migration
Migrate or port a WPF app to WinUI 3: namespaces (System.Windows to Microsoft.UI.Xaml), control mapping (DataGrid, WrapPanel, TabControl), Dispatcher to DispatcherQueue, imaging, MVVM with CommunityToolkit.Mvvm, ThemeResource. Use when converting WPF code or fixing migration build errors.
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.
runbook
Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things…
ai-deployment-patterns
Guides expert-level ai deployment patterns implementation: ai-ml and devops decision frameworks, production-ready patterns, and concrete templates for ai deployment patterns workflows. Use when the user asks about ai deployment patterns, ai deployment patterns configuration, or ai-ml best practices for ai projects. Do…
vercel-deploy
Ship a Next.js 16 App Router project to production on Vercel end-to-end: preview → smoke test → a staged production deployment (vercel --prod --skip-domain) that serves no traffic yet → vercel promote → domains and DNS, plus a rollback runbook. Requires stack.framework in {next, monorepo} and phase >= featurecomplete…
vercel-doctor
Run vercel-doctor on a Next.js project to find costly Vercel patterns BEFORE they inflate the bill, then route the fixes to the owning dev-flow skill (data-fetching for caching, design-md-to-app for images). The cost counterpart to compliance-audit (legal gate); dev-flow proposes it before a Vercel deploy. Use when…