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.
git 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/commands/attilaszasz/sdd-pilot/sddp-implement-qc-loop)<a href="https://agentmods.dev/commands/attilaszasz/sdd-pilot/sddp-implement-qc-loop"><img src="https://agentmods.dev/badge/commands/attilaszasz/sdd-pilot/sddp-implement-qc-loop/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/commands/attilaszasz/sdd-pilot/sddp-implement-qc-loop"><img src="https://agentmods.dev/badge/commands/attilaszasz/sdd-pilot/sddp-implement-qc-loop.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.00000 | $0.00397 |
| Opus 5.5 | $0.00000 | $0.00159 |
| Sonnet 5.5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
sddp-implement-qc-loop 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.
What it actually says
Command description: Run implement and QC in a continuous loop.
Argument hint: [optional: feature directory or branch name]
Command category: orchestration
Prerequisites: spec, plan, tasks
You are starting an Implement + QC loop workflow. Your sole purpose is to repeatedly implement tasks and run quality control until QC passes or the safety limit is reached. Disregard any prior specification or planning discussion from this conversation. Focus exclusively on the implement → QC cycle.
Load and follow the workflow in .github/sddp/workflows/implement-qc-loop/WORKFLOW.md.
The loop skill will instruct you to load and execute two sub-skills inline:
- Implement →
.github/sddp/workflows/implement-tasks/WORKFLOW.md - QC →
.github/sddp/workflows/quality-control/WORKFLOW.md
The selected agent dispatches each sub-skill Delegate target through its declared agents allowlist:
- Delegate: Context Gatherer →
.github/agents/_context-gatherer.md - Delegate: Task Tracker →
.github/agents/_task-tracker.md - Delegate: Developer →
.github/agents/_developer.md - Delegate: Checklist Reader →
.github/agents/_checklist-reader.md(only during gates.md checklist gate) - Delegate: Test Evaluator →
.github/agents/_test-evaluator.md(only during gates.md checklist gate, when checklists FAIL) - Delegate: Technical Researcher →
.github/agents/_technical-researcher.md - Delegate: QC Auditor →
.github/agents/_qc-auditor.md - Delegate: Story Verifier →
.github/agents/_story-verifier.md
Report progress to the user at each iteration boundary — summarize what was fixed and what remains.
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 · -6 lines · -9 tokens per session 3a5be7b15d41
- 1mo ago First seen · 34 lines · 9 tokens per session scan A 4fbc610be942
sddp-implement-qc-loop is a command published in the GitHub repository attilaszasz/sdd-pilot (98 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 397 tokens. 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 commands, from other repositories
review.speckit-test
Review the test automation implementation against the specification and the desired test pyramid shape; detect and explain misalignment - prioritise unit tests, identify high-value gaps and brittle tests, and provide actionable recommendations (including refactoring) to improve behavioural confidence.
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.
speckit.constitution
Create or update the project constitution from interactive or provided principle inputs.
inject-guidelines.command
Generate or refresh repository guideline documents using the project-guidelines-writer skill. Analyze the repo, generate all six standard guideline files by default, prefer managed-section updates for existing files, and ask only for exceptional overwrite or skip decisions.
build
Run /build — see .claude/commands/build.md for the authoritative spec.
validate
Run /validate — see .claude/commands/validate.md for the authoritative spec.