Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/commands/marctorrent/sprint-orchestrator/workstream-agent)<a href="https://agentmods.dev/commands/marctorrent/sprint-orchestrator/workstream-agent"><img src="https://agentmods.dev/badge/commands/marctorrent/sprint-orchestrator/workstream-agent.svg" alt="Measured on agentmods" height="20"></a>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.00027 | $0.00618 |
| Opus 5 | $0.00014 | $0.00309 |
| Sonnet 5 | $0.00005 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
workstream-agent 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workstream Agent Initializer
Run the sprint resume script to load workstream information, then provide agent instructions.
Step 1: Load Workstream Info
First, run the resume command to see workstream details:
pnpm sprint:resume {arg1}
Step 2: Navigate to Worktree
IMPORTANT: You must navigate to the worktree directory. Run this command:
cd ../worktrees/{arg1}
Verify you're in the correct location:
pwd # Should show: <project-root>/../worktrees/{arg1}
git branch # Should show: feature/{arg1}-workstream
Note: Worktrees are created in a sibling worktrees/ directory relative to the project root. The exact path depends on where you cloned the repository.
Step 3: Understand Your Role
You are a WORKSTREAM AGENT for this Sprint. You are NOT the main orchestrator.
Your Mission: Complete all tasks assigned to the {arg1} workstream.
Your Workflow
- Check your tasks: Look at the sprint:resume output for your assigned TASK-XXX items
- Implement each task sequentially: Follow TDD workflow (Red → Green → Refactor)
- Run quality gates after each task:
# Run your project's quality gates (configured in .claude/quality-gates.json) pnpm sprint:quality-gates # Examples for different project types: # Python: pytest && mypy . && ruff check . # Rust: cargo test && cargo check && cargo clippy # Go: go test ./... && go vet ./... # JavaScript/TypeScript: pnpm test run && pnpm type-check && pnpm lint && pnpm build - Commit after each completed task
- When ALL tasks complete: Run
pnpm sprint:complete {arg1}(runs quality gates automatically if enabled)
Important Boundaries
DO:
- ✅ Work ONLY on tasks assigned to the
{arg1}workstream - ✅ Commit after each completed task with proper format
- ✅ Run quality gates before each commit (use
pnpm sprint:quality-gatesor your project's commands) - ✅ Follow TDD: write tests first, then implementation
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 · 80 lines · 0 tokens per session scan A 7a713e104902
workstream-agent is a command published in the GitHub repository MarcTorrent/sprint-orchestrator (2 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 618 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.