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 attilaszasz/sdd-pilot --skill quality-assurancegit clone --depth 1 https://github.com/attilaszasz/sdd-pilotWrote 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/attilaszasz/sdd-pilot/quality-assurance)<a href="https://agentmods.dev/skills/attilaszasz/sdd-pilot/quality-assurance"><img src="https://agentmods.dev/badge/skills/attilaszasz/sdd-pilot/quality-assurance/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/attilaszasz/sdd-pilot/quality-assurance"><img src="https://agentmods.dev/badge/skills/attilaszasz/sdd-pilot/quality-assurance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.01579 |
| Opus 5 | $0.00018 | $0.00790 |
| Sonnet 5 | $0.00007 | $0.00316 |
| Haiku 4.5 | $0.00004 | $0.00158 |
Grade A, and why
quality-assurance 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 7d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Assurance Guide
Analysis Heuristics (/sddp-analyze)
When performing consistency analysis, verify the following relationships:
1. Spec vs. Plan Alignment
- Requirement Coverage: Does every P1/P2/P3 user story or objective in
spec.mdhave a corresponding section inplan.md? - Entity Matching: Do entities defined in
spec.md(Data Requirements) match thedata-model.md? - Complexity Check: If the spec marked a feature as "high complexity", does the plan include specific architectural mitigations?
2. Plan vs. Tasks Alignment
- Task Completeness: Does every section of the implementation plan have at least one corresponding task in
tasks.md? - Phase Ordering: Do tasks respect the allowed phase order (optional Setup → optional Foundational → Story Phases → optional Polish)?
- Missing Chunks: Are there major components in the architecture diagram that are absent from the task list?
3. Instructions Compliance
- Critical Violation: Any plan decision that contradicts
project-instructions.mdis a CRITICAL error. - Reporting: Flag these immediately with high severity.
Checklist Management (/sddp-checklist)
Checklists are the primary gate for the implementation phase.
Checklist Queue (.checklists)
The /sddp-plan agent generates a .checklists queue file in FEATURE_DIR/checklists/ that recommends checklist domains based on risk signals detected in the technical plan. This enables automated or sequential checklist generation without manual domain input.
- File:
FEATURE_DIR/checklists/.checklists - Format:
- [ ] CHL### Domain Name(e.g.,- [ ] CHL001 Security) - Generation:
/sddp-plancreates the file after the Post-Design Gate, capped by theMaxChecklistCountsetting in.github/sddp-config.md(default: 1). The plan agent may generate fewer entries if only fewer domains are relevant. - Consumption:
/sddp-checklistpicks the first unchecked entry when no explicit domain is provided, and marks it- [X]after completion. - Advisory, not blocking: The queue itself does not block implementation. Only the generated checklist files (
.md) inchecklists/are gating artifacts. - Override: An explicit domain argument to
/sddp-checklistalways takes priority over the queue.
What ships with it
1 file 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.
- 7d ago First seen · 94 lines · 36 tokens per session scan A 0335ea253206
quality-assurance is a skill published in the GitHub repository attilaszasz/sdd-pilot (96 stars, last pushed 6d ago), licensed MIT. It adds 36 tokens to every session and 1,579 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-09-03.
Other skills, from other repositories
spec-driven-task-implementer
Use this skill when an approved Spec-Driven change has reached Phase 4 and the user wants a task, phase, or full feature implemented from .specs/changes/ . It executes tasks in order, updates task status immediately, verifies each task before completion, and should not be used before implementation approval.
next
Phase 3 of the Tripod workflow, run repeatedly. Finds the first unchecked task in TASKS.md, implements it under the rules in CLAUDE.md, verifies its "Done when" condition, checks the box, and commits. Use when the user says "next task", "continue", "keep going", or invokes /tripod:next.
tasks
Phase 2 of the Tripod workflow. Reads SPEC.md and CLAUDE.md, then writes TASKS.md — an ordered list of small, scoped, verifiable tasks that implement the entire MVP. Use after the user has reviewed their spec, when they ask to "create tasks" or "break down the work", or when they invoke /tripod:tasks.
speckit-taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
speckit-converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
spec-kitty-implement-review
Orchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state transitions, rejection cycles, arbiter escalation, and dependency-aware sequencing across all 13 supported coding agents. Triggers: "implement and review WPs", "run the implement-review loop"…