agentmods.dev

setup-workflow

A project setup and maintenance command for a Git code repository and its agent-workflow files. It checks configuration, folders, documentation, hooks, prompts, and connected Atlassian tools.

In plain words
What is it for?
Use it to bootstrap a project, check its workflow setup, synchronize agent definitions, verify supporting files, and generate CLAUDE.md project instructions.
Why use it?
It reveals missing or outdated project infrastructure before the workflow depends on it and can be run repeatedly as the project changes.

Command for Claude Code

4 5mo ago B scan 32 tokens original MIT
View the source file ParkerM2/create-claude-workflow
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/parkerm2/create-claude-workflow/setup-workflow
Clone the repo
git clone --depth 1 https://github.com/ParkerM2/create-claude-workflow

Made for: Claude Code.

Per session 32 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,178 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00032 $0.02178
Opus 5 $0.00016 $0.01089
Sonnet 5 $0.00006 $0.00436
Haiku 4.5 $0.00003 $0.00218

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

Security

Grade B, and why

setup-workflow scanned grade B 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

- [ ] **Agent Teams**: Check `~/.claude/settings.json` for `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`
.claude/commands/setup-workflow.md · 167 lines

How it starts

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

/setup-workflow — Project Bootstrap Checklist

Comprehensive setup and maintenance for claude-workflow. Idempotent — safe to run multiple times. Each phase references its detailed flow rather than inlining it.

Phase 1: INVENTORY

Detect what exists before touching anything.

  • Git repo: git rev-parse --git-dir (halt if not a repo). Store REPO_ROOT, detect PRIMARY_BRANCH.
  • Config: Read .claude/workflow.json → classify: EXISTS / MISSING / MALFORMED
  • Directories: Check .claude/progress/, .claude/tracking/, .claude/agents/, .claude/docs/, .worktrees/
  • Docs: Check CLAUDE.md (projectRulesFile) and architecture file existence
  • Agent sync: Compare plugin agents/*.md vs .claude/agents/*.md — note missing/outdated
  • Hooks: Verify all hook files exist at <plugin-root>/hooks/ (active: config.js, tracker.js, ticket.js, workflow-enforcer.js, init-gate.js, safety-guard.js, hooks.json, tracking-emitter.js, proof-ledger.js, teammate-quality.js, task-validator.js, session-start.js, compact-reinject.js)
  • Prompts: Verify all 17 files in prompts/implementing-features/ exist (including AGENT-WORKFLOW-PHASES.md, THIN-SPAWN-TEMPLATE.md)
  • Agent Teams: Check ~/.claude/settings.json for CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
  • Atlassian: Check ~/.claude/settings.json for mcpServers.mcp-atlassian
  • Display gap report to user — show EXISTS/MISSING for each item

Phase 2: CONFIGURE

Create or update .claude/workflow.json. Follows the interactive flow from skills/workflow-setup/SKILL.md.

  • If config exists and is valid → display current values, ask "Update?" (skip if no)
  • If missing/malformed → run the 8-question interactive setup:
    1. Project rules file (default: CLAUDE.md)
    2. Architecture file (default: .claude/docs/ARCHITECTURE.md)
    3. Progress directory (default: .claude/progress)
    4. Branching strategy (Standard / Flat / Custom)
    5. Base branch (default: auto)
    6. Agent isolation (Worktrees / Shared)
    7. Branch enforcement (warn / block / off)
    8. Protected branches (default: main, master)
  • Write .claude/workflow.json with branching + guards sections per hooks/config.js defaults

Read the full file on GitHub · 167 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 · 167 lines · 32 tokens per session scan B 22ad886ca271

Subscribe to this mod's changes

setup-workflow is a command published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 2,178 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflowProductivityWriting and docs
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens