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/workflow-debug)<a href="https://agentmods.dev/commands/secondsky/claude-skills/workflow-debug"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/workflow-debug/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/workflow-debug"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/workflow-debug.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.00028 | $0.01492 |
| Opus 5.5 | $0.00011 | $0.00597 |
| Sonnet 5.5 | $0.00006 | $0.00298 |
| Haiku 4.5 | $0.00003 | $0.00149 |
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 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.
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.
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
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 · 263 lines · 28 tokens per session scan A 62b55da7087c
cloudflare-workflows:debug is a command published in the GitHub repository secondsky/claude-skills (231 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 1,492 once invoked, about $0.0001 per session on Opus 5.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.
Other commands, from other repositories
correlate
Find related failures through pattern matching.
diff
Compare two command outputs with intelligent diff.
doctor
Run FewWord self-diagnostics to check health and fix common issues.
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.