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-specify)<a href="https://agentmods.dev/commands/attilaszasz/sdd-pilot/sddp-specify"><img src="https://agentmods.dev/badge/commands/attilaszasz/sdd-pilot/sddp-specify/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-specify"><img src="https://agentmods.dev/badge/commands/attilaszasz/sdd-pilot/sddp-specify.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.00294 |
| Opus 5 | $0.00000 | $0.00147 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
sddp-specify 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 3d 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: Create a feature specification from a feature description.
Argument hint: [feature description]
Command category: feature-delivery
Prerequisites: project-instructions
You are starting a NEW specification workflow. Your sole purpose is to capture WHAT users, systems, or operators need and WHY — requirements, stories or objectives, and success criteria. Disregard any prior implementation context, code discussion, or task execution from this conversation. Do not write code, do not reference tasks, do not execute commands. Focus exclusively on the feature description and requirements.
$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/specify-feature/WORKFLOW.md.
The selected agent dispatches each Delegate target through its declared agents allowlist:
- Delegate: Context Gatherer →
.github/agents/_context-gatherer.md - Delegate: Spec Validator →
.github/agents/_spec-validator.md - Delegate: Policy Auditor →
.github/agents/_policy-auditor.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.
- 3d ago Changed · -3 lines · -9 tokens per session 1e2a44a19cbb
- 5d ago First seen · 25 lines · 9 tokens per session scan A e464062221bb
sddp-specify is a command published in the GitHub repository attilaszasz/sdd-pilot (95 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 294 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
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.
spec-driven.command
Start an approved Spec-Driven workflow using the brief or full lane.
speckit.companion.implement
Companion implement — execute tasks.md in dependency order, then mark complete.
grill
Universal intake interview: one type-shaped question at a time, each with a recommended answer, until the task is actually understood. Answers are written where they live (glossary, sparse ADRs, the goal draft's Context) the moment they resolve. Runs between type classification and the phase-0 Done= definition.
sdd-clarify
Adversarial pass over a finished spec — contradictions, ambiguity, untestable criteria, implementation posing as intent, missing failure modes.
speckit.assess.decide
Command "speckit.assess.decide" from github/spec-kit-copilot, covering when to run it, how to ask — always use the askuser tool, after the answers and what to ask about at the decide stage.