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 agentmods add skills/proffesor-for-testing/agentic-qe/sparc-methodologynpx skills add proffesor-for-testing/agentic-qe --skill sparc-methodologygit clone --depth 1 https://github.com/proffesor-for-testing/agentic-qeWrote 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/proffesor-for-testing/agentic-qe/sparc-methodology)<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/sparc-methodology"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/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 2d 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 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.
- 2d ago First seen · 119 lines · 79 tokens per session scan A 9c861dd4ab15
sparc-methodology is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (474 stars, last pushed 4d 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
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
tooluniverse-drug-research
Comprehensive drug profiling — mechanism, primary/secondary targets, drug interactions, clinical-trial status, adverse events (FAERS), pharmacogenomics, and approval history. Use for full drug investigation reports, 'tell me about drug X' queries, and assembling drug profiles for clinicians, researchers, or regulatory…
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
gh-bulk-issues
Orchestrate parallel Mastra Code headless instances to debug and fix multiple GitHub issues simultaneously.
qa-investigation
Investigate a specific test failure to its root cause and document the why. Detects whether a failing test is flaky (intermittent) or a deterministic bug during reproduction. Use when a test fails and you need the real cause, not just to make it green. Execution layer, not strategy review. Keywords: flaky test…