Borrowing it
Nothing to install: this file belongs to williamzujkowski/standards. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/williamzujkowski/standards/master/.claude/commands/sparc.mdgit clone --depth 1 https://github.com/williamzujkowski/standardsWrote 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/williamzujkowski/standards/sparc)<a href="https://agentmods.dev/commands/williamzujkowski/standards/sparc"><img src="https://agentmods.dev/badge/commands/williamzujkowski/standards/sparc/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.
<a href="https://agentmods.dev/commands/williamzujkowski/standards/sparc"><img src="https://agentmods.dev/badge/commands/williamzujkowski/standards/sparc.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.01280 |
| Opus 5.5 | $0.00005 | $0.00512 |
| Sonnet 5.5 | $0.00002 | $0.00256 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade A, and why
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 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.
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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚡️ SPARC Development Methodology
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.
SPARC Workflow
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
Available SPARC Modes
/sparc-architect- 🏗️ Architect/sparc-code- 🧠 Auto-Coder/sparc-tdd- 🧪 Tester (TDD)/sparc-debug- 🪲 Debugger/sparc-security-review- 🛡️ Security Reviewer/sparc-docs-writer- 📚 Documentation Writer/sparc-integration- 🔗 System Integrator/sparc-post-deployment-monitoring-mode- 📈 Deployment Monitor/sparc-refinement-optimization-mode- 🧹 Optimizer/sparc-ask- ❓Ask/sparc-devops- 🚀 DevOps/sparc-tutorial- 📘 SPARC Tutorial/sparc-supabase-admin- 🔐 Supabase Admin/sparc-spec-pseudocode- 📋 Specification Writer/sparc-mcp- ♾️ MCP Integration/sparc-sparc- ⚡️ SPARC Orchestrator
Quick Start
Option 1: Using MCP Tools (Preferred in Claude Code)
// Run SPARC orchestrator (default)
mcp__claude-flow__sparc_mode {
mode: "sparc",
task_description: "build complete authentication system"
}
// Run a specific mode
mcp__claude-flow__sparc_mode {
mode: "architect",
task_description: "design API structure"
}
// TDD workflow
mcp__claude-flow__sparc_mode {
mode: "tdd",
task_description: "implement user authentication",
options: {workflow: "full"}
}
Option 2: Using NPX CLI (Fallback when MCP not available)
# Run SPARC orchestrator (default)
npx claude-flow sparc "build complete authentication system"
# Run a specific mode
npx claude-flow sparc run architect "design API structure"
npx claude-flow sparc run tdd "implement user service"
# Execute full TDD workflow
npx claude-flow sparc tdd "implement user authentication"
# List all modes with details
npx claude-flow sparc modes --verbose
# For alpha features
npx claude-flow@alpha sparc run <mode> "your task"
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.
- yesterday First seen · 175 lines · 12 tokens per session scan A 841cd98e789e
sparc is a command published in the GitHub repository williamzujkowski/standards (18 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 1,280 once invoked, about $0.0000 per session on Opus 5.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-29.
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.