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 mattmre/EVOKORE-MCP-PUBLIC --skill sparc-pipelinegit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/mattmre/evokore-mcp-public/sparc-pipeline)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/sparc-pipeline"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/sparc-pipeline/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/skills/mattmre/evokore-mcp-public/sparc-pipeline"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/sparc-pipeline.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.00047 | $0.00677 |
| Opus 5 | $0.00023 | $0.00338 |
| Sonnet 5 | $0.00009 | $0.00135 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
sparc-pipeline 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 9d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sparc-pipeline — Full SPARC Development Pipeline
Runs all 5 SPARC phases sequentially with mandatory done-criteria gates between each phase. Suitable for features requiring structured, verifiable development.
Usage
/sparc-pipeline "feature name"
/sparc-pipeline "Implement multi-tenant session isolation"
The 5 Phases
Each phase produces a document in docs/session-phases/ and must pass its done-criteria gate before the next phase begins.
Phase 1: Specification
Produces: docs/session-phases/phase_1_<slug>.md
Done criteria gate:
- All FRs are testable (measurable acceptance criteria)
- NFRs have numeric thresholds
- Gherkin scenarios cover happy path + 3 edge cases
Phase 2: Pseudocode
Produces: docs/session-phases/phase_2_<slug>.md
Done criteria gate:
- Every FR has corresponding pseudocode
- Error states enumerated (no "TODO: handle errors")
- Algorithm complexity documented
Phase 3: Architecture
Produces: docs/session-phases/phase_3_<slug>.md
Done criteria gate:
- All component interfaces defined
- No circular dependencies
- ADR written for non-obvious design choices
Phase 4: Refinement (Implementation)
Produces: Working code + tests
Done criteria gate:
- All Gherkin scenarios from Phase 1 pass as vitest tests
- TypeScript compiles clean (
npx tsc --noEmit) - Truth score >= 0.90 (see verification-quality skill)
Phase 5: Completion
Produces: PR with all sections + updated docs
Done criteria gate:
- CI green (Build + TypeCheck + Tests pass)
- PR template sections filled (Description, Type of Change, Testing, Evidence)
- CLAUDE.md updated if any new patterns discovered
- next-session.md updated
Gate Failure Handling
If a phase fails its gate:
- Document the failure reason in the phase file
- Fix the gap in the current phase
- Re-check the gate criteria
- Do NOT proceed to the next phase until the gate passes
Output Summary
At completion, the pipeline produces:
- 3 phase documents (
phase_1,phase_2,phase_3) - Working code with full test coverage
- A merged PR
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.
- 9d ago First seen · 93 lines · 47 tokens per session scan A 5f74b6ff4477
sparc-pipeline is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 677 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-09-03.
Other skills, from other repositories
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) development methodology with multi-agent orchestration. Use when running a structured spec-to-code workflow or decomposing a feature through the SPARC phases.
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.