workflow-setup-assistant

workflow-setup-assistant is an agent for Claude Code from secondsky/claude-skills. It costs 37 tokens per session (2,537 once invoked), scanned A, original, MIT.

An automated setup assistant for Cloudflare Workflows in Cloudflare Worker projects. It detects the project's current files, creates workflow scaffolding, configures required connections, and prepares deployment.

In plain words
What is it for?
Use it when starting a new workflow, adding workflows to a Worker project, or configuring workflow infrastructure.
Why use it?
It reduces the manual work needed to determine what the project already has and add the missing workflow pieces.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./scripts/validate-workflow-config.sh wrangler.jsonc.

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

Good fit Use it when starting a new workflow, adding workflows to a Worker project, or configuring workflow infrastructure.

Compare 6 agents 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 agents/secondsky/claude-skills/workflow-setup-assistant

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 workflow-setup-assistant

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/secondsky/claude-skills/workflow-setup-assistant"><img src="https://agentmods.dev/badge/agents/secondsky/claude-skills/workflow-setup-assistant.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 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,537 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.00037 $0.02537
Opus 5.5 $0.00015 $0.01015
Sonnet 5.5 $0.00007 $0.00507
Haiku 4.5 $0.00004 $0.00254

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

Security

Grade A, and why

workflow-setup-assistant 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.

async fetch(req: Request, env: Env): Promise<Response> {
plugins/cloudflare-workflows/agents/workflow-setup-assistant.md · 482 lines

How it starts

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

Workflow Setup Assistant Agent

Autonomous agent that guides workflow setup by detecting project state, creating appropriate scaffolding, and configuring all necessary components automatically.

Trigger Conditions

This agent should be used when:

  • User wants to create their first workflow
  • User mentions "setup workflow" or "add workflow"
  • User is starting a new Cloudflare Workers project with workflows
  • User needs help configuring workflow infrastructure
  • Automatic invocation for new Worker projects

Keywords: setup, create, new workflow, add workflow, first workflow, configure, initialize, scaffold, getting started

Setup Process

Phase 1: Project Detection

Step 1.1: Check Project State
# Check for existing project files
ls -la 2>/dev/null | grep -E "wrangler|package|tsconfig"

Detect:

  • wrangler.jsonc or wrangler.toml → Existing Worker project
  • package.json → Node/Bun project
  • tsconfig.json → TypeScript project
  • None → New project needed
Step 1.2: Analyze Existing Configuration

If wrangler config exists:

# Check for existing workflows
grep -v '^\s*//' wrangler.jsonc | jq '.workflows // []'

# Check main entry point
grep -v '^\s*//' wrangler.jsonc | jq '.main'

# Check existing bindings
grep -v '^\s*//' wrangler.jsonc | jq 'keys'

Determine:

  • Are workflows already configured?
  • What's the main entry file?
  • What bindings exist (KV, D1, R2)?
Step 1.3: Decide Setup Path

Path A: New Project

  • No wrangler config found
  • Need to create entire project structure

Path B: Add Workflows to Existing Project

  • Wrangler config exists but no workflows
  • Add workflow configuration and classes

Path C: Add Another Workflow

  • Workflows already configured
  • Add new workflow to existing setup

Phase 2: Project Scaffolding (Path A)

If new project needed:

Step 2.1: Create Project Structure
mkdir -p src/workflows
mkdir -p test
Step 2.2: Create wrangler.jsonc

Read the full file on GitHub · 482 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 · 482 lines · 37 tokens per session scan A 02f9540d4b0a

Subscribe to this mod's changes

workflow-setup-assistant is an agent published in the GitHub repository secondsky/claude-skills (231 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 2,537 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.