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.
git clone --depth 1 https://github.com/secondsky/claude-skillsWrote 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/commands/secondsky/claude-skills/workers-deploy)<a href="https://agentmods.dev/commands/secondsky/claude-skills/workers-deploy"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/workers-deploy/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/commands/secondsky/claude-skills/workers-deploy"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/workers-deploy.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.00034 | $0.01611 |
| Opus 5.5 | $0.00014 | $0.00644 |
| Sonnet 5.5 | $0.00007 | $0.00322 |
| Haiku 4.5 | $0.00003 | $0.00161 |
Grade A, and why
cloudflare-workers:deploy 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 1mo 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.
curl -I [deployment-url] How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workers Deploy Command
Safe, guided deployment workflow for Cloudflare Workers with environment management and pre-deploy validation.
Execution Workflow
Phase 1: Environment Detection
Read and analyze the project configuration:
-
Check for wrangler config:
- Look for
wrangler.jsoncorwrangler.toml - If neither exists, abort: "No wrangler configuration found. Run
bunx wrangler initfirst."
- Look for
-
Parse environments:
- Extract environment configurations from wrangler config
- Identify: name, routes, vars, bindings for each environment
- Common environments: production, staging, dev, preview
-
Check current git status:
git status --porcelain- Warn if uncommitted changes exist
- Suggest committing before deploy
-
Check if wrangler is installed:
bunx wrangler --version- If fails, install will happen via bunx
Phase 2: Environment Selection
If --env argument provided:
- Use that environment
- Validate it exists in wrangler config
- If not found, abort with available environments list
If no --env argument: Use AskUserQuestion to select environment:
Question: "Which environment do you want to deploy to?"
- Options (dynamically generated from config):
production- Live environment (requires extra confirmation)staging- Pre-production testingdev- Development environment- [Any other envs found in config]
Phase 3: Pre-Deploy Validation
Ask user about pre-deploy checks:
Question: "Run pre-deploy validations?"
- Options:
- Run all checks (tests + types + build) (Recommended)
- Run tests only
- Run types only
- Skip validations (deploy immediately)
Based on selection, run:
Tests (if package.json has test script):
npm run test || bun test
- If tests fail, abort: "Tests failed. Fix issues before deploying."
- Allow user to override with confirmation
Type checking (if TypeScript project):
bunx tsc --noEmit
- If type errors, abort: "Type errors found. Fix before deploying."
- Allow user to override with confirmation
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.
- 1mo ago First seen · 279 lines · 34 tokens per session scan A a7067867b35a
cloudflare-workers:deploy is a command published in the GitHub repository secondsky/claude-skills (231 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,611 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other commands, from other repositories
correlate
Find related failures through pattern matching.
diff
Compare two command outputs with intelligent diff.
open
Open/retrieve an offloaded output by ID or shortcut.
search
Search through offloaded outputs with hard caps.
stats
Show FewWord session statistics with rich output and token savings.
config
Show effective FewWord configuration with sources.