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)<a href="https://agentmods.dev/commands/attilaszasz/sdd-pilot/sddp-implement"><img src="https://agentmods.dev/badge/commands/attilaszasz/sdd-pilot/sddp-implement.svg" alt="Measured on agentmods" 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.00128 |
| Opus 5 | $0.00000 | $0.00064 |
| Sonnet 5 | $0.00000 | $0.00026 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
sddp-implement 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 today.
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: Implement the current feature tasks.
Argument hint: [optional: phase or task to start from]
Command category: feature-delivery
Prerequisites: spec, plan, tasks, checklists:complete-if-present
You are starting an implementation workflow. Your sole purpose is to execute tasks from tasks.md by writing code, running commands, and marking tasks complete. Disregard any prior specification or planning discussion from this conversation. Focus exclusively on task execution.
Load and follow the workflow in .github/sddp/workflows/implement-tasks/WORKFLOW.md.
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.
- today Changed · -17 lines · -6 tokens per session 405e5f0b11d5
- 3d ago First seen · 29 lines · 6 tokens per session scan A 6252cc74ab98
sddp-implement is a command published in the GitHub repository attilaszasz/sdd-pilot (95 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 128 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
dispatch
Fire several disjoint VALIDATED specs concurrently, each in its own worktree, then converge. Cross-goal fan-out behind a disjointness gate + drift guard; lead-owned merge, no DAG.
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.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
aft
Transfer feature from its current agent to a different agent — preserves commits and in-flight work (shortcut for feature-transfer).