cloudflare-workflows:debug

cloudflare-workflows:debug is a command for coding agents from secondsky/claude-skills. It costs 28 tokens per session (1,492 once invoked), scanned A, original, MIT.

An interactive troubleshooting command for deployed Cloudflare Workflow instances. It lists or identifies instances, retrieves their details, and guides diagnosis of failures or stuck runs.

In plain words
What is it for?
Use it when a deployed workflow fails, becomes stuck, or needs instance-level investigation.
Why use it?
It gives a structured way to investigate a specific workflow run instead of searching through deployment output alone.

Command

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

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.

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

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:debug

README.md
[![agentmods](https://agentmods.dev/badge/commands/secondsky/claude-skills/workflow-debug.svg)](https://agentmods.dev/commands/secondsky/claude-skills/workflow-debug)
Your own site
<a href="https://agentmods.dev/commands/secondsky/claude-skills/workflow-debug"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/workflow-debug.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,492 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00028 $0.01492
Opus 5 $0.00014 $0.00746
Sonnet 5 $0.00006 $0.00298
Haiku 4.5 $0.00003 $0.00149

Measured yesterday against content hash 62b55da7087c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cloudflare-workflows:debug 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 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.

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.

plugins/cloudflare-workflows/commands/workflow-debug.md · 263 lines

How it starts

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

Workflow Debug

Overview

Interactive debugging assistant for Cloudflare Workflow instances with step-by-step diagnosis.

Prerequisites

  • wrangler CLI authenticated
  • Workflow deployed to Cloudflare
  • Instance ID or workflow name

Steps

Step 1: Identify Instance

Use AskUserQuestion:

Question: "Which workflow instance needs debugging?"

  • Header: "Instance"
  • Question: "How would you like to identify the instance?"
  • multiSelect: false
  • Options:
    • label: "I have instance ID"

    • description: "Provide specific instance ID to debug"

    • label: "Show recent instances"

    • description: "List recent instances and select one"

    • label: "Show failed instances"

    • description: "List only failed instances"

If "I have instance ID":

  • Ask for: workflow name + instance ID

If "Show recent instances":

wrangler workflows instances list ${workflowName} --limit 10

Display instances, ask user to select one

If "Show failed instances":

wrangler workflows instances list ${workflowName} --status errored --limit 10

Step 2: Fetch Instance Details

wrangler workflows instances describe ${workflowName} ${instanceId}

Parse Output:

  • Status (running, complete, errored)
  • Error message (if failed)
  • Step history (which steps completed)
  • Last step executed
  • Retry count

Display:

Instance Details:
- ID: ${instanceId}
- Status: ${status}
- Steps Completed: ${stepsCompleted} / ${totalSteps}
- Last Step: ${lastStep}
- Error: ${errorMessage}

Step 3: Diagnose Issue

Based on status, provide diagnosis:

If Status = "errored":

Check error message patterns:

Pattern 1: "Cannot perform I/O on behalf of different request"

  • Diagnosis: I/O outside step.do()
  • Solution: Move I/O inside step.do() callbacks
  • Reference: Load references/common-issues.md #1

Pattern 2: "NonRetryableError"

  • Diagnosis: Permanent failure
  • Solution: Check error message, fix root cause
  • Reference: Load references/common-issues.md #3

Read the full file on GitHub · 263 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. yesterday First seen · 263 lines · 28 tokens per session scan A 62b55da7087c

Subscribe to this mod's changes

cloudflare-workflows:debug is a command published in the GitHub repository secondsky/claude-skills (214 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 1,492 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.