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.
git clone --depth 1 https://github.com/frankxai/agentic-creator-osWrote 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/frankxai/agentic-creator-os/ask)<a href="https://agentmods.dev/commands/frankxai/agentic-creator-os/ask"><img src="https://agentmods.dev/badge/commands/frankxai/agentic-creator-os/ask/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.
<a href="https://agentmods.dev/commands/frankxai/agentic-creator-os/ask"><img src="https://agentmods.dev/badge/commands/frankxai/agentic-creator-os/ask.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00031 | $0.00681 |
| Opus 5.5 | $0.00012 | $0.00272 |
| Sonnet 5.5 | $0.00006 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
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 1mo 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.
This is a copy
100% identical to sparc-ask — 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
❓Ask
Role Definition
You are a task-formulation guide that helps users navigate, ask, and delegate tasks to the correct SPARC modes.
Custom Instructions
Guide users to ask questions using SPARC methodology:
• 📋 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
Available Tools
- read: File reading and viewing
Usage
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "ask",
task_description: "help me choose the right mode",
options: {
namespace: "ask",
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 ask "help me choose the right mode"
# For alpha features
npx claude-flow@alpha sparc run ask "help me choose the right mode"
# With namespace
npx claude-flow sparc run ask "your task" --namespace ask
# Non-interactive mode
npx claude-flow sparc run ask "your task" --non-interactive
Option 3: Local Installation
# If claude-flow is installed locally
./claude-flow sparc run ask "help me choose the right mode"
Memory Integration
Using MCP Tools (Preferred)
// Store mode-specific context
mcp__claude-flow__memory_usage {
action: "store",
key: "ask_context",
value: "important decisions",
namespace: "ask"
}
// Query previous work
mcp__claude-flow__memory_search {
pattern: "ask",
namespace: "ask",
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.
- 1mo ago First seen · 98 lines · 31 tokens per session scan A 2d785fada820
sparc-ask is a command published in the GitHub repository frankxai/agentic-creator-os (12 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 681 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to sparc-ask, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks. Scope it to a release's changes with a git range ( .. ) or changes for the uncommitted working tree; audit the whole repository for the first release or…
document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply. check mode writes nothing and reports where the existing docs and the code disagree.
performance-audit-static
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact. Scope it to a release's changes with a git range ( .. ) or changes for the uncommitted working tree; audit the whole repository for the first…
proof-points
Pull proof points from decks/battlecards, register, verify, or audit the claims your messaging relies on — then deepen brain Section 6 argument-hint: ".
experiment
Build, audit, or score a growth experiment document.
interview-summary
Summarize a customer interview transcript using JTBD analysis.