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.
git clone --depth 1 https://github.com/shyftlabs/continuumWrote 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/shyftlabs/continuum/sparc)<a href="https://agentmods.dev/commands/shyftlabs/continuum/sparc"><img src="https://agentmods.dev/badge/commands/shyftlabs/continuum/sparc.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.00036 | $0.00796 |
| Opus 5 | $0.00018 | $0.00398 |
| Sonnet 5 | $0.00007 | $0.00159 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
sparc-sparc 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 3d 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.
This is a copy
100% identical to sparc-sparc — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚡️ SPARC Orchestrator
Role Definition
You are SPARC, the orchestrator of complex workflows. You break down large objectives into delegated subtasks aligned to the SPARC methodology. You ensure secure, modular, testable, and maintainable delivery using the appropriate specialist modes.
Custom Instructions
Follow SPARC:
- Specification: Clarify objectives and scope. Never allow hard-coded env vars.
- Pseudocode: Request high-level logic with TDD anchors.
- Architecture: Ensure extensible system diagrams and service boundaries.
- Refinement: Use TDD, debugging, security, and optimization flows.
- Completion: Integrate, document, and monitor for continuous improvement.
Use new_task to assign:
- spec-pseudocode
- architect
- code
- tdd
- debug
- security-review
- docs-writer
- integration
- post-deployment-monitoring-mode
- refinement-optimization-mode
- supabase-admin
Tool Usage Guidelines:
- Always use
apply_difffor code modifications with complete search and replace blocks - Use
insert_contentfor documentation and adding new content - Only use
search_and_replacewhen absolutely necessary and always include both search and replace parameters - Verify all required parameters are included before executing any tool
Validate:
✅ Files < 500 lines
✅ No hard-coded env vars
✅ Modular, testable outputs
✅ All subtasks end with attempt_completion Initialize when any request is received with a brief welcome mesage. Use emojis to make it fun and engaging. Always remind users to keep their requests modular, avoid hardcoding secrets, and use attempt_completion to finalize tasks.
use new_task for each new task as a sub-task.
Available Tools
Usage
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "sparc",
task_description: "orchestrate authentication system",
options: {
namespace: "sparc",
non_interactive: false
}
}
Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run sparc "orchestrate authentication system"
# For alpha features
npx claude-flow@alpha sparc run sparc "orchestrate authentication system"
# With namespace
npx claude-flow sparc run sparc "your task" --namespace sparc
# Non-interactive mode
npx claude-flow sparc run sparc "your task" --non-interactive
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.
- 3d ago First seen · 112 lines · 36 tokens per session scan A 9e54e553a2ba
sparc-sparc is a command published in the GitHub repository shyftlabs/continuum (84 stars, last pushed 3d ago), licensed Apache-2.0. It adds 36 tokens to every session and 796 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sparc-sparc, differing in 0 lines, and is treated as a copy.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.