cloudflare-workflows:test

cloudflare-workflows:test is a command for Claude Code from secondsky/claude-skills. It costs 33 tokens per session (2,171 once invoked), scanned A, original, MIT.

An interactive testing command for Cloudflare Workflows, which run multi-step jobs with saved progress and retries. It tests workflows locally or on Cloudflare, validates their behavior, and collects measurements.

In plain words
What is it for?
Use it to test a selected workflow with a local Worker or a deployed instance and review its execution results and metrics.
Why use it?
It helps catch workflow problems and check execution behavior before or after deployment.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the AskUserQuestion tool; positional $N argument.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is - Benchmark: ./scripts/benchmark-workflow.sh ${workflowName} 10.

Part of the cloudflare-workflows plugin — 1 skill, 4 commands, 3 agents shipped together

Good fit Use it to test a selected workflow with a local Worker or a deployed instance and review its execution results and metrics.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/secondsky/claude-skills
agentmods
npx agentmods add commands/secondsky/claude-skills/workflow-test

Made for: Claude Code.

Or install cloudflare-workflows, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 3 agents.

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-workflows:test

README.md
[![agentmods](https://agentmods.dev/badge/commands/secondsky/claude-skills/workflow-test/github.svg)](https://agentmods.dev/commands/secondsky/claude-skills/workflow-test)
Your own site
<a href="https://agentmods.dev/commands/secondsky/claude-skills/workflow-test"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/workflow-test/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-workflows:test

Your own site · 80×15
<a href="https://agentmods.dev/commands/secondsky/claude-skills/workflow-test"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/workflow-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,171 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.00033 $0.02171
Opus 5.5 $0.00013 $0.00868
Sonnet 5.5 $0.00007 $0.00434
Haiku 4.5 $0.00003 $0.00217

Measured 1mo ago against content hash 28c625b09973, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cloudflare-workflows:test 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 -X POST "http://localhost:8787" \
plugins/cloudflare-workflows/commands/workflow-test.md · 383 lines

How it starts

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

Workflow Test

Overview

Interactive testing for Cloudflare Workflows with execution monitoring and validation.

Prerequisites

  • wrangler CLI authenticated
  • Workflow deployed (for remote testing)
  • Worker running locally (for local testing)

Steps

Step 1: Select Workflow

Use AskUserQuestion:

Question: "Which workflow would you like to test?"

  • Header: "Workflow"
  • Question: "Select workflow to test"
  • multiSelect: false
  • Options:
    • label: "List available workflows"

    • description: "Show workflows from wrangler.jsonc"

    • label: "Enter workflow name"

    • description: "Type workflow name manually"

If "List available workflows":

# Parse wrangler.jsonc
grep -A 3 "workflows" wrangler.jsonc | grep "name"

Display list, ask user to select


Step 2: Choose Test Type

Use AskUserQuestion:

Question: "How would you like to test?"

  • Header: "Test Type"
  • Question: "Choose testing environment"
  • multiSelect: false
  • Options:
    • label: "Local Testing (Recommended)"

    • description: "Test with wrangler dev (fast, safe)"

    • label: "Remote Testing"

    • description: "Test deployed workflow (production)"

    • label: "Both"

    • description: "Local first, then remote"

Store as: testType


Step 3: Configure Test Parameters

Use AskUserQuestion:

Question: "Provide test parameters"

  • Header: "Parameters"
  • Question: "Enter workflow parameters as JSON"
  • multiSelect: false
  • Options:
    • label: "Use default test data"

    • description: "Simple test with id: 'test-123'"

    • label: "Custom JSON"

    • description: "I'll provide specific test data"

If "Custom JSON":

  • Ask user to input JSON string
  • Validate JSON syntax
  • Store as: testParams

If "Use default":

{
  "id": "test-123",
  "timestamp": "${currentTimestamp}"
}

Step 4: Run Local Test (if selected)

Start dev server:

# Start wrangler dev in background
wrangler dev &
DEV_PID=$!

# Wait for startup
sleep 3

Read the full file on GitHub · 383 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. 1mo ago First seen · 383 lines · 33 tokens per session scan A 28c625b09973

Subscribe to this mod's changes

cloudflare-workflows:test is a command published in the GitHub repository secondsky/claude-skills (231 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 2,171 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.