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 Soulcynics404/AgentForge --skill sparc-methodologygit clone --depth 1 https://github.com/Soulcynics404/AgentForgeWrote 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/soulcynics404/agentforge/sparc-methodology)<a href="https://agentmods.dev/skills/soulcynics404/agentforge/sparc-methodology"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/sparc-methodology.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.00079 | $0.00759 |
| Opus 5 | $0.00039 | $0.00380 |
| Sonnet 5 | $0.00016 | $0.00152 |
| Haiku 4.5 | $0.00008 | $0.00076 |
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 4d 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-methodology — 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sparc Methodology Skill
Purpose
SPARC development workflow: Specification, Pseudocode, Architecture, Refinement, Completion. A structured approach for complex implementations that ensures thorough planning before coding.
When to Trigger
- new feature implementation
- complex implementations
- architectural changes
- system redesign
- integration work
- unclear requirements
When to Skip
- simple bug fixes
- documentation updates
- configuration changes
- well-defined small tasks
- routine maintenance
Commands
Specification Phase
Define requirements, acceptance criteria, and constraints
npx @claude-flow/cli hooks route --task "specification: [requirements]"
Example:
npx @claude-flow/cli hooks route --task "specification: user authentication with OAuth2, MFA, and session management"
Pseudocode Phase
Write high-level pseudocode for the implementation
npx @claude-flow/cli hooks route --task "pseudocode: [feature]"
Example:
npx @claude-flow/cli hooks route --task "pseudocode: OAuth2 login flow with token refresh"
Architecture Phase
Design system structure, interfaces, and dependencies
npx @claude-flow/cli hooks route --task "architecture: [design]"
Example:
npx @claude-flow/cli hooks route --task "architecture: auth module with service layer, repository, and API endpoints"
Refinement Phase
Iterate on the design based on feedback
npx @claude-flow/cli hooks route --task "refinement: [feedback]"
Example:
npx @claude-flow/cli hooks route --task "refinement: add rate limiting and brute force protection"
Completion Phase
Finalize implementation with tests and documentation
npx @claude-flow/cli hooks route --task "completion: [final checks]"
Example:
npx @claude-flow/cli hooks route --task "completion: verify all tests pass, update API docs, security review"
SPARC Coordinator
Spawn SPARC coordinator agent
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 119 lines · 79 tokens per session scan A 9c861dd4ab15
sparc-methodology is a skill published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 15d ago), licensed MIT. It adds 79 tokens to every session and 759 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sparc-methodology, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
browser-automation
Playwright-based browser automation patterns for autonomous web interaction.
clip-hand-skill
Expert knowledge for AI video clipping — yt-dlp downloading, whisper transcription, SRT generation, and ffmpeg processing.
twitter-hand-skill
Expert knowledge for AI Twitter/X management — API v2 reference, content strategy, engagement playbook, safety, and performance tracking.
package-author
A packaging guide for turning scripts, skills, or an MCP service into a standard plugin package. MCP is a way for an AI assistant to connect to external tools.
slack-tools
Slack workspace management and automation specialist.
routing-card-authoring
Use whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager. States what belongs in every field, which fields the hub can actually match on, and which fields silently break matching when a sentence leaks into them.