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-qc)<a href="https://agentmods.dev/commands/attilaszasz/sdd-pilot/sddp-qc"><img src="https://agentmods.dev/badge/commands/attilaszasz/sdd-pilot/sddp-qc/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-qc"><img src="https://agentmods.dev/badge/commands/attilaszasz/sdd-pilot/sddp-qc.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.00293 |
| Opus 5 | $0.00000 | $0.00147 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
sddp-qc 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.
What it actually says
Command description: Run quality control against the implemented feature.
Argument hint: [optional: testing focus such as unit tests, security audit, requirements sync]
Command category: feature-delivery
Prerequisites: spec, plan, tasks, implementation:complete
You are starting a Quality Control workflow. Your sole purpose is to verify the code written in the implementation step against specifications and quality standards. Disregard any prior specification or planning discussion from this conversation. Focus exclusively on quality control.
Load and follow the workflow in .github/sddp/workflows/quality-control/WORKFLOW.md.
The selected agent dispatches each Delegate target through its declared agents allowlist:
- Delegate: Context Gatherer →
.github/agents/_context-gatherer.md - Delegate: QC Auditor →
.github/agents/_qc-auditor.md - Delegate: Story Verifier →
.github/agents/_story-verifier.md
Browser tool availability is determined at runtime by the active probe in Step 6.0 of the shared QC workflow. If the integration's native browser tool (e.g., VS Code web) or an MCP browser server is reachable, browser runtime validation will be used automatically. No static browser declaration is needed from this adapter.
Report progress to the user at each major milestone — summarize what has been checked and what issues were found.
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 Changed · -2 lines · -8 tokens per session 0839cab5803a
- 7d ago First seen · 23 lines · 8 tokens per session scan A 322edad9e9c0
sddp-qc is a command published in the GitHub repository attilaszasz/sdd-pilot (96 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 293 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
speckit.companion.living-coverage
Report living-spec requirement→test coverage — per requirement, whether its coverage tier maps a test (opt-in, read-only, never halts).
battery
The full independent-verification battery for a finished branch: a fresh-context acceptance verifier that RE-EXECUTES the verification commands against a stated baseline, a multi-lens review (single-pass minimum, domain lenses on escalation), and the advisor extra lens, dispatched in parallel at prescribed model…
speckit.companion.living-validate
Check the shape of living specs and a feature spec's deltas — a requirement with no scenario, a scenario missing WHEN or THEN, a duplicate heading, a delta pointing at nothing (opt-in, read-only, never halts).
tdd
Test-driven development with tests that actually catch breaks: red before green, name the break each test catches, and the mutation check before done.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
verify
Re-run the test levels (task-verifier + integration-verifier + acceptance-verifier + system-verifier) on the current spec/branch read-only, no rebuild. The on-demand executor of the complete V-model right arm.