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 ayushcodes10/echo-mem --skill sparc-methodologygit clone --depth 1 https://github.com/ayushcodes10/echo-memWrote 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/ayushcodes10/echo-mem/sparc-methodology)<a href="https://agentmods.dev/skills/ayushcodes10/echo-mem/sparc-methodology"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/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/ayushcodes10/echo-mem/sparc-methodology"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/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.00030 | $0.06039 |
| Opus 5.5 | $0.00012 | $0.02416 |
| Sonnet 5.5 | $0.00006 | $0.01208 |
| Haiku 4.5 | $0.00003 | $0.00604 |
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 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
95% identical to sparc-methodology — 91 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 — 1,107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SPARC Methodology - Comprehensive Development Framework
Overview
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) is a systematic development methodology integrated with Codex Flow's multi-agent orchestration capabilities. It provides 17 specialized modes for comprehensive software development, from initial research through deployment and monitoring.
Table of Contents
- Core Philosophy
- Development Phases
- Available Modes
- Activation Methods
- Orchestration Patterns
- TDD Workflows
- Best Practices
- Integration Examples
- Common Workflows
Core Philosophy
SPARC methodology emphasizes:
- Systematic Approach: Structured phases from specification to completion
- Test-Driven Development: Tests written before implementation
- Parallel Execution: Concurrent agent coordination for 2.8-4.4x speed improvements
- Memory Integration: Persistent knowledge sharing across agents and sessions
- Quality First: Comprehensive reviews, testing, and validation
- Modular Design: Clean separation of concerns with clear interfaces
Key Principles
- Specification Before Code: Define requirements and constraints clearly
- Design Before Implementation: Plan architecture and components
- Tests Before Features: Write failing tests, then make them pass
- Review Everything: Code quality, security, and performance checks
- Document Continuously: Maintain current documentation throughout
Development Phases
Phase 1: Specification
Goal: Define requirements, constraints, and success criteria
- Requirements analysis
- User story mapping
- Constraint identification
- Success metrics definition
- Pseudocode planning
Key Modes: researcher, analyzer, memory-manager
Phase 2: Architecture
Goal: Design system structure and component interfaces
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 Changed 19834c95dd55
- 1mo ago First seen · 1,107 lines · 30 tokens per session scan A eb858ef5f83e
sparc-methodology is a skill published in the GitHub repository ayushcodes10/echo-mem (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 6,039 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to sparc-methodology, differing in 91 lines, and is treated as a copy.
Other skills, from other repositories
tdd-with-memory
A test-first implementation workflow that recalls past decisions, conventions, and lessons before coding. TDD, or test-driven development, means writing a failing test first, then implementing the code and finally cleaning it up.
bad-case-to-dpo
A guide to turning failed production agent runs into training and evaluation data. It explains how to find the first mistake, create preference examples for DPO (Direct Preference Optimization), and check that a fix does not damage other tasks.
pre-pr
Prepare a Honcho change for a pull request to plastic-labs/honcho. Invoke before opening a PR, when drafting a PR body, when asked if a branch is PR-ready, or when filling the pull request template. Checks the linked issue, required tests and docs, then writes Description / Proofs / Fixes.
taste
Use when implementing any feature, bugfix, or behavior change, before writing the implementation code. Especially use under pressure - production is down, "just make it work", "quick fix" - which is when it gets skipped.
memmesh-integrate
Integrate MemMesh into an existing repository using a goal-driven, test-first (TDD) pipeline. Detects the repo's language/stack, asks whether to use MemMesh Hosted (SDK, managed) or Local (CLI + MCP over SQLite), writes failing tests before any implementation, and lands additive, feature-flag-gated code that a…
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.