spec-workflow-setup

spec-workflow-setup is a command for Claude Code from qdhenry/Claude-Command-Suite. It costs 0 tokens per session (2,785 once invoked), scanned C, original, no licence file.

An installation and configuration guide for connecting the spec-workflow MCP server to Claude Code. MCP is a way for an AI coding tool to connect to an external task-management service.

In plain words
What is it for?
Use it when integrating spec-workflow with Claude Code and configuring its server connection.
Why use it?
It helps set up the connection needed to use spec-workflow's task management and parallel execution features.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it when integrating spec-workflow with Claude Code and configuring its server connection.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/qdhenry/claude-command-suite/spec-workflow-setup
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.

Clone the repo
git clone --depth 1 https://github.com/qdhenry/Claude-Command-Suite

Made for: Claude Code.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/qdhenry/claude-command-suite/spec-workflow-setup"><img src="https://agentmods.dev/badge/commands/qdhenry/claude-command-suite/spec-workflow-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 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,785 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown 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.00000 $0.02785
Opus 5 $0.00000 $0.01392
Sonnet 5 $0.00000 $0.00557
Haiku 4.5 $0.00000 $0.00279

Measured 5d ago against content hash f1f86a62de12, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade C, and why

spec-workflow-setup scanned grade C with 2 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 5d 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.

Reads agent configuration directoriesmediumAgent snooping

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

**Location:** `~/.claude/settings.json`

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

cat > .mcp.json << 'EOF'
.claude/commands/spec-workflow/spec-workflow-setup.md · 480 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 5d ago First seen · 480 lines · 0 tokens per session scan C f1f86a62de12

Subscribe to this mod's changes

spec-workflow-setup is a command published in the GitHub repository qdhenry/Claude-Command-Suite (1,333 stars, last pushed 6mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 2,785 tokens. A static security scan graded it C with 2 findings (reads agent configuration directories, reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.