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-methodologygit 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-methodology)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/sparc-methodology"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/sparc-methodology/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-methodology"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/sparc-methodology.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.00036 | $0.00561 |
| Opus 5 | $0.00018 | $0.00280 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
sparc-methodology 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 11d 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.
What it actually says
SPARC Methodology Skill
A 5-phase structured development approach that ensures correctness at each stage before proceeding.
Trigger
Use this skill when:
- Starting a complex feature with unclear requirements
- Refactoring a large system component
- Building multi-service integrations
- Onboarding to an unfamiliar codebase
The 5 Phases
Phase 1: Specification (S)
Output: phase_1_{slug}.md
Produces: Functional Requirements (FR-01..FR-N), Non-Functional Requirements (NFR-01..NFR-N), Gherkin scenarios (Given/When/Then), acceptance criteria.
Done criteria:
- All FRs are testable
- NFRs have measurable thresholds
- Gherkin scenarios cover happy path + top 3 edge cases
Phase 2: Pseudocode (P)
Output: phase_2_{slug}.md
Produces: Language-agnostic algorithm representation, data flow diagram, error handling strategy.
Done criteria:
- Pseudocode covers every FR
- Error states enumerated
- No ambiguous "do magic here" blocks
Phase 3: Architecture (A)
Output: phase_3_{slug}.md
Produces: Component diagram, interface contracts, dependency graph, ADR for key decisions.
Done criteria:
- All interfaces defined
- No circular dependencies
- ADR written for any non-obvious choice
Phase 4: Refinement (R)
Output: Working code + tests
Produces: Implementation iterating from pseudocode, test cases from Gherkin, TypeScript type-safe.
Done criteria:
- All Gherkin scenarios pass
- TypeScript compiles clean
- Truth score >= 0.90
Phase 5: Completion (C)
Output: PR + docs
Produces: PR with all sections filled, docs updated, CLAUDE.md updated if patterns changed.
Done criteria:
- CI green
- PR review checklist complete
- next-session.md updated
Usage
/sparc-spec "{feature name}" → Runs Phase 1 only
/sparc-pipeline "{feature name}" → Runs all 5 phases sequentially with gate checks
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.
- 11d ago First seen · 76 lines · 36 tokens per session scan A fb6cf9e07c6e
sparc-methodology is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 561 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 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.