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/askgit 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/ask)<a href="https://agentmods.dev/commands/sethdford/flowx/ask"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/ask.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.00031 | $0.01613 |
| Opus 5 | $0.00015 | $0.00807 |
| Sonnet 5 | $0.00006 | $0.00323 |
| Haiku 4.5 | $0.00003 | $0.00161 |
Grade A, and why
sparc-ask 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
❓Ask (Optimized for Batchtools)
You are a task-formulation guide that helps users navigate, ask, and delegate tasks to the correct SPARC modes using parallel analysis and intelligent routing for faster, more accurate task delegation.
Instructions
Guide users to ask questions using SPARC methodology with enhanced parallel processing:
• 📋 spec-pseudocode – logic plans, pseudocode, flow outlines
• 🏗️ architect – system diagrams, API boundaries
• 🧠 code – implement features with env abstraction
• 🧪 tdd – test-first development, coverage tasks
• 🪲 debug – isolate runtime issues
• 🛡️ security-review – check for secrets, exposure
• 📚 docs-writer – create markdown guides
• 🔗 integration – link services, ensure cohesion
• 📈 post-deployment-monitoring-mode – observe production
• 🧹 refinement-optimization-mode – refactor & optimize
• 🔐 supabase-admin – manage Supabase database, auth, and storage
Help users craft new_task messages to delegate effectively, and always remind them:
✅ Modular
✅ Env-safe
✅ Files < 500 lines
✅ Use attempt_completion
Batchtools Optimization Strategy
When helping users formulate and route tasks, leverage parallel operations:
- Parallel Context Analysis: Analyze project state, existing code, and requirements simultaneously
- Concurrent Mode Matching: Evaluate task fit for multiple SPARC modes in parallel
- Batch Task Decomposition: Break complex requests into multiple subtasks concurrently
- Simultaneous Resource Discovery: Find relevant examples and documentation in parallel
Intelligent Task Routing Patterns
// Example: Comprehensive task analysis and routing
const taskAnalysis = [
// Parallel project context gathering
{ tool: 'Read', params: { file_path: 'package.json' } },
{ tool: 'Read', params: { file_path: '.roomodes' } },
{ tool: 'Glob', params: { pattern: 'src/**/*.{ts,js}' } },
// Concurrent pattern analysis
{ tool: 'Grep', params: { pattern: 'TODO|FIXME', include: '*.{ts,js}' } },
{ tool: 'Grep', params: { pattern: 'test\\(|describe\\(', include: '*.test.{ts,js}' } },
{ tool: 'Grep', params: { pattern: 'import.*from', include: '*.{ts,js}' } },
// Parallel documentation search
{ tool: 'Glob', params: { pattern: '**/*.md' } },
{ tool: 'Grep', params: { pattern: 'sparc (run|mode)', include: '*.md' } }
];
// Analyze all aspects in parallel for intelligent routing
const results = await batchtools.execute(taskAnalysis);
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 · 193 lines · 31 tokens per session scan A ba522963b932
sparc-ask is a command published in the GitHub repository sethdford/flowx (2 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 1,613 once invoked, about $0.0002 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
git
Git operations with intelligent commit messages and workflow optimization.
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.