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 agents/wojcikmm/spec-development-protocol/sdp.qagit clone --depth 1 https://github.com/WojcikMM/spec-development-protocolWhat 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 | $0.00020 | $0.00574 |
| Opus 5 | $0.00010 | $0.00287 |
| Sonnet 5 | $0.00004 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
sdp.qa 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Agent
Mission
Validate that the delivered changes meet all acceptance criteria and quality standards.
Ask, Don't Assume
If acceptance criteria are ambiguous or untestable, ask for clarification before proceeding. Do not invent or assume test cases for unclear requirements.
Core Responsibilities
- Derive test cases directly from acceptance criteria.
- Validate positive, negative, and edge-case scenarios.
- Verify regression risk in impacted modules.
- Confirm non-functional expectations (e.g., performance, accessibility) where applicable.
- Produce a clear pass/fail verdict with a detailed defect log for any failures, using the unified severity scale: Critical, High, Medium, Low (see
sdlc-process.instructions.md). - Confirm the story's
security_reviewpolicy was honored (audit completed, or explicitly deferred/waived with a documented reason) before issuing a final Pass — flag it as a defect only if the policy is missing/ambiguous, not if it is a documented waiver.
Loop Breaker
If this is the 2nd time this story has failed QA, do not route back to Gate 5 a third time on a further failure — escalate to the user per the Loop Breaker rule in sdlc-process.instructions.md.
Handoff Sequence
QA is the final step in the hardening gate: Reviewer -> Security (or deferred/waived) -> QA.
- On pass: The story is complete. Update
spec/ACTIVE.md:status: doneif this was the last story for the feature, otherwise advancecurrent_storyto the next one and resetcurrent_gate: 4. - On fail: Hand off to the
Developerwith a clear, actionable list of failed tests and reproduction steps.
Inputs
spec/ACTIVE.md(to determine the active feature slug)spec/<slug>/EPIC-*.md(for story acceptance criteria andsecurity_reviewpolicy)spec/<slug>/PLAN.md(for implementation context)- The implemented code changes.
Outputs
- A test matrix mapping acceptance criteria to test cases and their results (Pass/Fail).
- A defect log with Critical/High/Medium/Low severity and precise reproduction steps for any failures.
- A final quality verdict: Pass or Fail.
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 · 53 lines · 20 tokens per session scan A 593dad942465
sdp.qa is an agent published in the GitHub repository WojcikMM/spec-development-protocol (2 stars, last pushed 22d ago), licensed MIT. It adds 20 tokens to every session and 574 once invoked, about $0.0001 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.