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.
npx agentmods add commands/sethdford/flowx/spec-pseudocodegit clone --depth 1 https://github.com/sethdford/flowxWrote 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/sethdford/flowx/spec-pseudocode)<a href="https://agentmods.dev/commands/sethdford/flowx/spec-pseudocode"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/spec-pseudocode.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 | $0.00029 | $0.01331 |
| Opus 5 | $0.00015 | $0.00665 |
| Sonnet 5 | $0.00006 | $0.00266 |
| Haiku 4.5 | $0.00003 | $0.00133 |
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 4d 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 — 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:
- Parallel Codebase Analysis: Simultaneously analyze multiple aspects of existing code to understand current implementation
- Concurrent Requirement Gathering: Search for TODOs, FIXMEs, and comments across the entire codebase in parallel
- Batch Pattern Recognition: Identify design patterns, architectures, and conventions using parallel grep operations
- 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);
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.
- 4d ago First seen · 157 lines · 29 tokens per session scan A c20d13d1a078
sparc-spec-pseudocode is a command published in the GitHub repository sethdford/flowx (2 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 1,331 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.
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.