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/f-amine/vibe-stack/spec-pseudocodegit clone --depth 1 https://github.com/f-amine/vibe-stackWrote 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/f-amine/vibe-stack/spec-pseudocode)<a href="https://agentmods.dev/commands/f-amine/vibe-stack/spec-pseudocode"><img src="https://agentmods.dev/badge/commands/f-amine/vibe-stack/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.00564 |
| Opus 5 | $0.00015 | $0.00282 |
| Sonnet 5 | $0.00006 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00056 |
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 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.
This is a copy
100% identical to sparc-spec-pseudocode — 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 Specification Writer
Role Definition
You capture full project context—functional requirements, edge cases, constraints—and translate that into modular pseudocode with TDD anchors.
Custom 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.
Available Tools
- read: File reading and viewing
- edit: File modification and creation
Usage
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "spec-pseudocode",
task_description: "define payment flow requirements",
options: {
namespace: "spec-pseudocode",
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 spec-pseudocode "define payment flow requirements"
# For alpha features
npx claude-flow@alpha sparc run spec-pseudocode "define payment flow requirements"
# With namespace
npx claude-flow sparc run spec-pseudocode "your task" --namespace spec-pseudocode
# Non-interactive mode
npx claude-flow sparc run spec-pseudocode "your task" --non-interactive
Option 3: Local Installation
# If claude-flow is installed locally
./claude-flow sparc run spec-pseudocode "define payment flow requirements"
Memory Integration
Using MCP Tools (Preferred)
// Store mode-specific context
mcp__claude-flow__memory_usage {
action: "store",
key: "spec-pseudocode_context",
value: "important decisions",
namespace: "spec-pseudocode"
}
// Query previous work
mcp__claude-flow__memory_search {
pattern: "spec-pseudocode",
namespace: "spec-pseudocode",
limit: 5
}
Using NPX CLI (Fallback)
# Store mode-specific context
npx claude-flow memory store "spec-pseudocode_context" "important decisions" --namespace spec-pseudocode
# Query previous work
npx claude-flow memory query "spec-pseudocode" --limit 5
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 · 81 lines · 29 tokens per session scan A d60a693ba51f
sparc-spec-pseudocode is a command published in the GitHub repository f-amine/vibe-stack (21 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 564 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sparc-spec-pseudocode, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
new
Scaffold a new Better-T-Stack project. Plans a full, validated stack with the Better-T-Stack MCP server, confirms it, then generates the project.
add
Add addons/features (PWA, Tauri, docs, linters, task runners, MCP, …) to an existing Better-T-Stack project via the Better-T-Stack MCP server.
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.