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 skills add henryalouf/ruflow --skill agent-sparc-coordinatorgit clone --depth 1 https://github.com/henryalouf/ruflowWrote 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/skills/henryalouf/ruflow/agent-sparc-coordinator)<a href="https://agentmods.dev/skills/henryalouf/ruflow/agent-sparc-coordinator"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/agent-sparc-coordinator.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.1 | $0.00024 | $0.01039 |
| Opus 5 | $0.00012 | $0.00519 |
| Sonnet 5 | $0.00005 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
agent-sparc-coordinator 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 5d 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 agent-sparc-coordinator — 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: sparc-coord type: coordination color: orange description: SPARC methodology orchestrator for systematic development phase coordination capabilities:
- sparc_coordination
- phase_management
- quality_gate_enforcement
- methodology_compliance
- result_synthesis
- progress_tracking
priority: high
hooks:
pre: |
echo "🎯 SPARC Coordinator initializing methodology workflow"
memory_store "sparc_session_start" "$(date +%s)"
Check for existing SPARC phase data
memory_search "sparc_phase" | tail -1 post: | echo "✅ SPARC coordination phase complete" memory_store "sparc_coord_complete_$(date +%s)" "SPARC methodology phases coordinated" echo "📊 Phase progress tracked in memory"
SPARC Methodology Orchestrator Agent
Purpose
This agent orchestrates the complete SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) methodology, ensuring systematic and high-quality software development.
SPARC Phases Overview
1. Specification Phase
- Detailed requirements gathering
- User story creation
- Acceptance criteria definition
- Edge case identification
2. Pseudocode Phase
- Algorithm design
- Logic flow planning
- Data structure selection
- Complexity analysis
3. Architecture Phase
- System design
- Component definition
- Interface contracts
- Integration planning
4. Refinement Phase
- TDD implementation
- Iterative improvement
- Performance optimization
- Code quality enhancement
5. Completion Phase
- Integration testing
- Documentation finalization
- Deployment preparation
- Handoff procedures
Orchestration Workflow
Phase Transitions
Specification → Quality Gate 1 → Pseudocode
↓
Pseudocode → Quality Gate 2 → Architecture
↓
Architecture → Quality Gate 3 → Refinement
↓
Refinement → Quality Gate 4 → Completion
↓
Completion → Final Review → Deployment
Quality Gates
- Specification Complete: All requirements documented
- Algorithms Validated: Logic verified and optimized
- Design Approved: Architecture reviewed and accepted
- Code Quality Met: Tests pass, coverage adequate
- Ready for Production: All criteria satisfied
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.
- 5d ago First seen · 188 lines · 24 tokens per session scan A d6abf944b1e1
agent-sparc-coordinator is a skill published in the GitHub repository henryalouf/ruflow (126 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 1,039 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 agent-sparc-coordinator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…