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-projectplan)<a href="https://agentmods.dev/commands/attilaszasz/sdd-pilot/sddp-projectplan"><img src="https://agentmods.dev/badge/commands/attilaszasz/sdd-pilot/sddp-projectplan/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-projectplan"><img src="https://agentmods.dev/badge/commands/attilaszasz/sdd-pilot/sddp-projectplan.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.00196 |
| Opus 5 | $0.00000 | $0.00098 |
| Sonnet 5 | $0.00000 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
sddp-projectplan 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: Decompose the project into prioritized epics and execution waves.
Argument hint: [additional context or constraints for epic decomposition]
Command category: project-bootstrap
Prerequisites: product-document:planning-ready, technical-context:planning-ready
You are starting a project planning workflow. Your sole purpose is to decompose the product into prioritized, dependency-ordered epics based on existing bootstrap artifacts. Disregard feature-level implementation context from this conversation. Focus exclusively on epic decomposition, dependency analysis, wave planning, and coverage validation.
$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/project-planning/WORKFLOW.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 · -12 tokens per session 0197b1a77e93
- 6d ago First seen · 19 lines · 12 tokens per session scan A 94b9636e009e
sddp-projectplan is a command published in the GitHub repository attilaszasz/sdd-pilot (96 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 196 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.specify
Companion specify — a feature spec with prioritized user stories.
speckit.companion.tasks
Companion tasks — user-story phased task list.
speckit.companion.doctor
Report on a spec's run health — unfinished steps, unjournaled tasks, step bleed, drift you can judge, a step that closed having verified nothing, a step that closed without the file it promised, and why completion did not land (read-only, retroactive, never halts).
speckit.companion.after-specify
Capture the current spec-kit step into .spec-context.json for the Companion GUI.
speckit.companion.classify
Classify the change size (simple | normal | oversized) so the Companion workflow can right-size the pipeline.
assign
Turn a backlog item (ID-NNN) into a scoped goal draft and route it into the right WORKFLOW lane. Writes .claude/goals/, never executes.