A command for managing parallel workstreams, which are separate lines of project work handled at the same time. It can list, create, switch, track, complete, and resume them.

Use it to create workstreams, switch between them, check progress, archive completed work, and resume paused work.

It keeps concurrent work organised so you can see what is active and return to the right workstream.

workstreams — Command for Claude Code by luanpdd

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/luanpdd/kit-mcp

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/luanpdd/kit-mcp/workstreams/github.svg)](https://agentmods.dev/commands/luanpdd/kit-mcp/workstreams)

Your own site

<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/workstreams"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/workstreams/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/workstreams"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/workstreams.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 474 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00019	$0.00474
Opus 5	$0.00010	$0.00237
Sonnet 5	$0.00004	$0.00095
Haiku 4.5	$0.00002	$0.00047

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

Security

Grade A, and why

workstreams 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 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.

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.

kit/framework/commands/workstreams.md · 64 lines

What it actually says

/workstreams

Manage parallel workstreams for concurrent milestone work.

Usage

/workstreams [subcommand] [args]

Subcommands

Command	Description
`list`	List all workstreams with status
`create <name>`	Create a new workstream
`status <name>`	Detailed status for one workstream
`switch <name>`	Set active workstream
`progress`	Progress summary across all workstreams
`complete <name>`	Archive a completed workstream
`resume <name>`	Resume work in a workstream

Step 1: Parse Subcommand

Parse the user's input to determine which workstream operation to perform. If no subcommand given, default to list.

Step 2: Execute Operation

list

Run: node "$TOOLS" workstream list --raw --cwd "$CWD" Display the workstreams in a table format showing name, status, current phase, and progress.

create

Run: node "$TOOLS" workstream create <name> --raw --cwd "$CWD" After creation, display the new workstream path and suggest next steps:

/new-milestone --ws <name> to set up the milestone

status

Run: node "$TOOLS" workstream status <name> --raw --cwd "$CWD" Display detailed phase breakdown and state information.

switch

Run: node "$TOOLS" workstream set <name> --raw --cwd "$CWD" Also set WORKSTREAM env var for the current session.

progress

Run: node "$TOOLS" workstream progress --raw --cwd "$CWD" Display a progress overview across all workstreams.

complete

Run: node "$TOOLS" workstream complete <name> --raw --cwd "$CWD" Archive the workstream to milestones/.

resume

Set the workstream as active and suggest /resume-work --ws <name>.

Step 3: Display Results

Format the JSON output from tools into a human-readable display. Include the ${WS} flag in any routing suggestions.

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.

5d ago First seen · 64 lines · 19 tokens per session scan A 6c6a5a1b5941

Subscribe to this mod's changes

workstreams is a command published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 474 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-09-03.

Project management mcp

workstreams