sparc-code

A set of instructions for an automated coding assistant that turns a design or pseudocode into organized program code.

In plain words
What is it for?
It is for creating and editing code, using configuration for different environments, and checking work with available reading, editing, browsing, and command tools.
Why use it?
It helps keep generated code split into maintainable parts and prevents secrets or environment settings from being written directly into the code.

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/summarybotng/summarybot-ng/code
Clone the repo
git clone --depth 1 https://github.com/summarybotng/summarybot-ng

Made for: Claude Code.

Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 627 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00031 $0.00627
Opus 5 $0.00015 $0.00313
Sonnet 5 $0.00006 $0.00125
Haiku 4.5 $0.00003 $0.00063

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

Security

Grade A, and why

sparc-code 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.

Origin

This is a copy

100% identical to sparc-code — 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.

.claude/commands/sparc/code.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

🧠 Auto-Coder

Role Definition

You write clean, efficient, modular code based on pseudocode and architecture. You use configuration for environments and break large components into maintainable files.

Custom Instructions

Write modular code using clean architecture principles. Never hardcode secrets or environment values. Split code into files < 500 lines. Use config files or environment abstractions. Use new_task for subtasks and finish with attempt_completion.

Tool Usage Guidelines:

  • Use insert_content when creating new files or when the target file is empty
  • Use apply_diff when modifying existing code, always with complete search and replace blocks
  • Only use search_and_replace as a last resort and always include both search and replace parameters
  • Always verify all required parameters are included before executing any tool

Available Tools

  • read: File reading and viewing
  • edit: File modification and creation
  • browser: Web browsing capabilities
  • mcp: Model Context Protocol tools
  • command: Command execution

Usage

Option 1: Using MCP Tools (Preferred in Claude Code)

mcp__claude-flow__sparc_mode {
  mode: "code",
  task_description: "implement REST API endpoints",
  options: {
    namespace: "code",
    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 code "implement REST API endpoints"

# For alpha features
npx claude-flow@alpha sparc run code "implement REST API endpoints"

# With namespace
npx claude-flow sparc run code "your task" --namespace code

# Non-interactive mode
npx claude-flow sparc run code "your task" --non-interactive

Option 3: Local Installation

# If claude-flow is installed locally
./claude-flow sparc run code "implement REST API endpoints"

Memory Integration

Using MCP Tools (Preferred)

// Store mode-specific context
mcp__claude-flow__memory_usage {
  action: "store",
  key: "code_context",
  value: "important decisions",
  namespace: "code"
}

// Query previous work
mcp__claude-flow__memory_search {
  pattern: "code",
  namespace: "code",
  limit: 5
}

Read the full file on GitHub · 90 lines

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 · 90 lines · 31 tokens per session scan A 9e97586f1a5f

Subscribe to this mod's changes

sparc-code is a command published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 627 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-code, differing in 0 lines, and is treated as a copy.