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 commands/secondsky/claude-skills/workflow-setupgit 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/workflow-setup)<a href="https://agentmods.dev/commands/secondsky/claude-skills/workflow-setup"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/workflow-setup.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.00040 | $0.04074 |
| Opus 5 | $0.00020 | $0.02037 |
| Sonnet 5 | $0.00008 | $0.00815 |
| Haiku 4.5 | $0.00004 | $0.00407 |
Grade A, and why
cloudflare-workflows:setup 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 yesterday.
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.
async fetch(req: Request, env: Env): Promise<Response> { How it starts
The opening of the file, as written. The whole thing — 669 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Setup Wizard
Overview
Complete interactive setup wizard for Cloudflare Workflows: project initialization, configuration, class scaffolding, and deployment preparation.
Prerequisites
Check before starting:
- Cloudflare account with wrangler authenticated (
wrangler whoami) - Node.js/Bun installed
- Existing Worker project OR willingness to create one
- Write access to wrangler.jsonc
Steps
Step 1: Project Detection
Check if this is a new or existing project:
# Check for wrangler.jsonc
if [ -f "wrangler.jsonc" ]; then
EXISTING_PROJECT=true
else
EXISTING_PROJECT=false
fi
# Check for package.json
if [ -f "package.json" ]; then
HAS_PACKAGE_JSON=true
else
HAS_PACKAGE_JSON=false
fi
If new project ($EXISTING_PROJECT == false):
Use AskUserQuestion:
- Question: "No Worker project detected. Create new project?"
- Options:
- "Yes - Create new Worker project" → Run
npm create cloudflare@latest - "No - I'll set up manually" → Exit with setup instructions
- "Yes - Create new Worker project" → Run
If existing project: Continue to Step 2
Step 2: Gather Workflow Requirements
Use AskUserQuestion to collect setup preferences.
Question 1: Workflow Name
- Header: "Workflow Name"
- Question: "What should your workflow be named?"
- multiSelect: false
- Options:
- label: "Custom name (I'll type it)"
- description: "Enter a unique workflow name (e.g., order-processing, user-onboarding)"
Capture input: Ask user to provide workflow name
- Validation: Must be lowercase, alphanumeric + hyphens only (
^[a-z0-9-]+$) - Store as:
workflowName - Generate:
className= PascalCase version (e.g., "order-processing" → "OrderProcessing")
Question 2: Workflow Purpose
- Header: "Workflow Type"
- Question: "What type of workflow are you building?"
- multiSelect: false
- Options:
- label: "Sequential Processing"
- description: "Multi-step data processing with automatic retries"
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.
- yesterday First seen · 669 lines · 40 tokens per session scan A f7cb7774fdb8
cloudflare-workflows:setup is a command published in the GitHub repository secondsky/claude-skills (214 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 4,074 once invoked, about $0.0002 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-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.
timeline
Visual timeline of command outputs in current session.