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-systemdesign)<a href="https://agentmods.dev/commands/attilaszasz/sdd-pilot/sddp-systemdesign"><img src="https://agentmods.dev/badge/commands/attilaszasz/sdd-pilot/sddp-systemdesign/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-systemdesign"><img src="https://agentmods.dev/badge/commands/attilaszasz/sdd-pilot/sddp-systemdesign.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.00189 |
| Opus 5 | $0.00000 | $0.00095 |
| Sonnet 5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
sddp-systemdesign 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 or refine the canonical software architecture document.
Argument hint: [project description, docs, constraints, or architecture inputs]
Command category: project-bootstrap
Prerequisites: none
Start the project system-design workflow. Create or refine the canonical project-level technical context, ignoring feature-level implementation detail. Stay focused on project architecture and reusable technical baselines.
$ARGUMENTS = the user's prompt text for this command. If none was provided, set $ARGUMENTS to empty and let the skill handle the gap.
Follow .github/sddp/workflows/system-design/WORKFLOW.md.
Do not browse ad hoc. Only perform external research when the workflow says Delegate: Technical Researcher; at that point read .github/agents/_technical-researcher.md and perform only that delegated step.
Report progress at major milestones with what is complete 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 · -4 lines · -9 tokens per session f299b3425975
- 6d ago First seen · 21 lines · 9 tokens per session scan A 82af671f3535
sddp-systemdesign 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 189 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.
docs
Update all project documentation to match the current codebase. Cross-references the diff against every doc file and fixes drift.