sp.orchestrate

A command that coordinates software work across different agents and stages using spec-driven development, a process that starts with written requirements and a plan. It chooses an agent based on the work and project stage.

In plain words
What is it for?
Use it to route planning, writing, engineering, and platform tasks through a coordinated development workflow.
Why use it?
It helps divide work between suitable agents while keeping the process aligned with the project’s stated rules.

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/mjunaidca/taskforce/sp.orchestrate
Clone the repo
git clone --depth 1 https://github.com/mjunaidca/taskforce

Made for: Claude Code.

Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 9,738 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
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 $0.00054 $0.09738
Opus 5 $0.00027 $0.04869
Sonnet 5 $0.00011 $0.01948
Haiku 4.5 $0.00005 $0.00974

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

Security

Grade B, and why

sp.orchestrate 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.

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

ls -la .claude/skills/
.claude/commands/sp.orchestrate.md · 1,142 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. yesterday First seen · 1,142 lines · 54 tokens per session scan B 9def290467b0

Subscribe to this mod's changes

sp.orchestrate is a command published in the GitHub repository mjunaidca/taskforce (10 stars, last pushed 7mo ago), with no licence file. It adds 54 tokens to every session and 9,738 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.