start

A command that starts or discovers a workflow session and creates the files needed to track it.

In plain words
What is it for?
Use it to start a standard, review, TDD, test, or documentation session, discover an existing one, or deliberately create a new session.
Why use it?
It prevents conflicting sessions and sets up project and session records before work begins.

Command for Claude Code

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/catlog22/claude-code-workflow/start
Clone the repo
git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow

Made for: Claude Code.

Per session 17 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,830 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.00017 $0.01830
Opus 5 $0.00009 $0.00915
Sonnet 5 $0.00003 $0.00366
Haiku 4.5 $0.00002 $0.00183

Measured 2d ago against content hash 0153d8ccc085, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

start 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 2d 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.

.claude/commands/workflow/session/start.md · 203 lines

How it starts

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

Start Workflow Session (/workflow:session:start)

Overview

Manages workflow sessions with three operation modes: discovery (manual), auto (intelligent), and force-new.

Dual Responsibility:

  1. Project-level initialization (first-time only): Creates .workflow/project-tech.json for feature registry
  2. Session-level initialization (always): Creates session directory structure

Session Types

The --type parameter classifies sessions for CCW dashboard organization:

Type Description Default For
workflow Standard implementation (default) workflow-plan skill
review Code review sessions review-cycle skill
tdd TDD-based development workflow-tdd-plan skill
test Test generation/fix sessions workflow-test-fix skill
docs Documentation sessions memory-manage skill

Validation: If --type is provided with invalid value, return error:

ERROR: Invalid session type. Valid types: workflow, review, tdd, test, docs

Step 0: Initialize Project State (First-time Only)

Executed before all modes - Ensures project-level state files exist by calling /workflow:spec:setup.

Check and Initialize

# Check if project state exists (both files required)
bash(test -f .workflow/project-tech.json && echo "TECH_EXISTS" || echo "TECH_NOT_FOUND")
bash(test -f .ccw/specs/*.md && echo "GUIDELINES_EXISTS" || echo "GUIDELINES_NOT_FOUND")

If either NOT_FOUND, delegate to /workflow:spec:setup:

// Call workflow:spec:setup for intelligent project analysis
Skill(skill="workflow:spec:setup");

// Wait for init completion
// project-tech.json and specs/*.md will be created

Output:

  • If BOTH_EXIST: PROJECT_STATE: initialized
  • If NOT_FOUND: Calls /workflow:spec:setup → creates:
    • .workflow/project-tech.json with full technical analysis
    • .ccw/specs/*.md with empty scaffold

Note: /workflow:spec:setup uses cli-explore-agent to build comprehensive project understanding (technology stack, architecture, key components). This step runs once per project. Subsequent executions skip initialization.

Read the full file on GitHub · 203 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. 2d ago First seen · 203 lines · 0 tokens per session scan A 0153d8ccc085

Subscribe to this mod's changes

start is a command published in the GitHub repository catlog22/Claude-Code-Workflow (2,135 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 1,830 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-08-30.