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-testgit 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-test)<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="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.00033 | $0.02171 |
| Opus 5 | $0.00016 | $0.01086 |
| Sonnet 5 | $0.00007 | $0.00434 |
| Haiku 4.5 | $0.00003 | $0.00217 |
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 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.
curl -X POST "http://localhost:8787" \ 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
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 · 383 lines · 33 tokens per session scan A 28c625b09973
cloudflare-workflows:test is a command published in the GitHub repository secondsky/claude-skills (214 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 2,171 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.