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-checklist)<a href="https://agentmods.dev/commands/attilaszasz/sdd-pilot/sddp-checklist"><img src="https://agentmods.dev/badge/commands/attilaszasz/sdd-pilot/sddp-checklist/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-checklist"><img src="https://agentmods.dev/badge/commands/attilaszasz/sdd-pilot/sddp-checklist.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.00266 |
| Opus 5.5 | $0.00000 | $0.00106 |
| Sonnet 5.5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
sddp-checklist 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: Generate and evaluate a requirements quality checklist.
Argument hint: [optional: quality focus or feature context]
Command category: feature-delivery
Prerequisites: spec, plan
You are starting a quality checklist workflow. Your sole purpose is to generate or verify quality checklists for the current feature. Disregard any prior context from this conversation. Focus exclusively on requirements quality and completeness.
$ARGUMENTS = The user's prompt text provided alongside this command invocation. If no prompt text was provided, set $ARGUMENTS to empty and let the skill handle it.
Load and follow the workflow in .github/sddp/workflows/generate-checklist/WORKFLOW.md.
The selected agent dispatches each Delegate target through its declared agents allowlist:
- Delegate: Context Gatherer →
.github/agents/_context-gatherer.md - Delegate: Test Planner →
.github/agents/_test-planner.md - Delegate: Test Evaluator →
.github/agents/_test-evaluator.md - Delegate: Technical Researcher →
.github/agents/_technical-researcher.md
Report progress to the user at each major milestone — summarize what has been completed 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 · -3 lines · -8 tokens per session 0359e9ce17d2
- 1mo ago First seen · 25 lines · 8 tokens per session scan A 3ba501a77ed2
sddp-checklist is a command published in the GitHub repository attilaszasz/sdd-pilot (98 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 266 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.
release
Prepare and publish spec-driven-steroids through the tag-triggered npm release pipeline.
archive
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.
inject-guidelines.command
Review repository guidelines using the project-guidelines-writer skill. Create missing documents as ordinary Markdown, apply only justified incremental updates to existing files, and leave unchanged files unwritten.
build
Run /build — see .claude/commands/build.md for the authoritative spec.
spec-driven.command
Start an approved Spec-Driven workflow using the brief or full lane.