sparc-spec-pseudocode

sparc-spec-pseudocode is a command for Claude Code from sethdford/flowx. It costs 29 tokens per session (1,331 once invoked), scanned A, original, MIT.

A command for turning project requirements into modular pseudocode documents, with planned testing points. Pseudocode is a plain-language outline of how code should work, and TDD means writing tests as part of the design process.

In plain words
What is it for?
It is for analyzing an existing codebase, finding unfinished work, documenting module behavior, and creating phase-by-phase specifications for future coding and tests.
Why use it?
It helps clarify requirements, edge cases, and constraints before implementation begins.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Good fit It is for analyzing an existing codebase, finding unfinished work, documenting module behavior, and creating phase-by-phase specifications for future coding and tests.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/sethdford/flowx/spec-pseudocode
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.

Clone the repo
git clone --depth 1 https://github.com/sethdford/flowx

Made for: Claude Code.

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.

agentmods badge for sparc-spec-pseudocode

README.md
[![agentmods](https://agentmods.dev/badge/commands/sethdford/flowx/spec-pseudocode/github.svg)](https://agentmods.dev/commands/sethdford/flowx/spec-pseudocode)
Your own site
<a href="https://agentmods.dev/commands/sethdford/flowx/spec-pseudocode"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/spec-pseudocode/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.

agentmods 80×15 button for sparc-spec-pseudocode

Your own site · 80×15
<a href="https://agentmods.dev/commands/sethdford/flowx/spec-pseudocode"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/spec-pseudocode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,331 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original 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.1 $0.00029 $0.01331
Opus 5.5 $0.00012 $0.00532
Sonnet 5.5 $0.00006 $0.00266
Haiku 4.5 $0.00003 $0.00133

Measured 2mo ago against content hash c20d13d1a078, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sparc-spec-pseudocode 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 2mo 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.

src/templates/claude-optimized/.claude/commands/sparc/spec-pseudocode.md · 157 lines

How it starts

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

📋 Specification Writer (Optimized for Batchtools)

You capture full project context—functional requirements, edge cases, constraints—and translate that into modular pseudocode with TDD anchors using parallel analysis and batch operations for comprehensive specification generation.

Instructions

Write pseudocode as a series of md files with phase_number_name.md and flow logic that includes clear structure for future coding and testing. Split complex logic across modules. Never include hard-coded secrets or config values. Ensure each spec module remains < 500 lines.

Batchtools Optimization Strategy

When creating specifications, leverage parallel operations:

  1. Parallel Codebase Analysis: Simultaneously analyze multiple aspects of existing code to understand current implementation
  2. Concurrent Requirement Gathering: Search for TODOs, FIXMEs, and comments across the entire codebase in parallel
  3. Batch Pattern Recognition: Identify design patterns, architectures, and conventions using parallel grep operations
  4. Simultaneous Spec Generation: Create multiple specification documents concurrently for different modules

Workflow Patterns

// Example: Comprehensive project specification
const analysisTask = [
  // Parallel analysis of project structure
  { tool: 'Glob', params: { pattern: '**/*.{ts,js,tsx,jsx}' } },
  { tool: 'Glob', params: { pattern: '**/package.json' } },
  { tool: 'Glob', params: { pattern: '**/*.test.*' } },
  
  // Concurrent search for key patterns
  { tool: 'Grep', params: { pattern: 'TODO|FIXME|HACK', include: '*.{ts,js}' } },
  { tool: 'Grep', params: { pattern: 'class.*extends|interface.*{', include: '*.ts' } },
  { tool: 'Grep', params: { pattern: 'export (default |const |function |class)', include: '*.{ts,js}' } },
  
  // Parallel configuration analysis
  { tool: 'Read', params: { file_path: 'package.json' } },
  { tool: 'Read', params: { file_path: 'tsconfig.json' } },
  { tool: 'Read', params: { file_path: '.env.example' } }
];

// Execute comprehensive analysis in parallel
const results = await batchtools.execute(analysisTask);

Read the full file on GitHub · 157 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. 2mo ago First seen · 157 lines · 29 tokens per session scan A c20d13d1a078

Subscribe to this mod's changes

sparc-spec-pseudocode is a command published in the GitHub repository sethdford/flowx (2 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 1,331 once invoked, about $0.0001 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-08-31.

Related

sparc-spec-pseudocode compared with commands from other repositories

sparc-spec-pseudocode next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
sparc-spec-pseudocodesethdford/flowxCommand23mo agoMITA29Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code