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.
npx skills add attilaszasz/sdd-pilot --skill sddp-autopilotgit 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/skills/attilaszasz/sdd-pilot/sddp-autopilot)<a href="https://agentmods.dev/skills/attilaszasz/sdd-pilot/sddp-autopilot"><img src="https://agentmods.dev/badge/skills/attilaszasz/sdd-pilot/sddp-autopilot/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/skills/attilaszasz/sdd-pilot/sddp-autopilot"><img src="https://agentmods.dev/badge/skills/attilaszasz/sdd-pilot/sddp-autopilot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 30 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00030 | $0.00696 |
| Opus 5 | $0.00015 | $0.00348 |
| Sonnet 5 | $0.00006 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
sddp-autopilot 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 11d 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
Argument hint: [optional: feature description; omit to select the first unchecked epic]
Command category: orchestration
Prerequisites: autopilot:enabled, product-document:planning-ready, technical-context:planning-ready
You are running the Autopilot Pipeline — a fully automated SDD workflow that executes all phases (Specify → Clarify → Plan → Checklist → Tasks → Analyze → Implement+QC) in a single uninterrupted turn without user interaction. Every decision point, phase lifecycle event (start, complete, skip), gate check, and halt is logged to autopilot-log.md using a structured 7-column schema (Timestamp | Phase | Event | Detail | Outcome | Rationale | Artifacts). Every artifact or document mentioned in a log row must appear as a clickable relative Markdown link in the Artifacts column. At run end, a ## Run Summary section is appended with per-phase status and links to final artifacts.
Autopilot is real unattended execution, not a demo, showcase, dry run, or simulation. Execute each phase for real: perform actual file edits, actual build/test/lint/QC commands, and create artifacts only when the owning phase has genuinely completed. Never simulate implementation, QC, test results, or marker creation. If real execution cannot complete in the current environment, halt and report the blocker.
Load and follow the workflow in .github/sddp/workflows/autopilot-pipeline/WORKFLOW.md.
Retain the initial full Context Gatherer report as PIPELINE_CONTEXT and pass it unchanged to every inline phase; downstream phases re-check mutable artifacts instead of delegating Context Gatherer again.
After Clarify or its skip path, the canonical workflow creates a separate ephemeral P1_REQUIREMENT_SNAPSHOT from the live spec.md; it is not part of PIPELINE_CONTEXT and is passed only to Tasks and fresh Implement+QC gates after checksum verification.
The pipeline skill will instruct you to load and execute these sub-skills inline, in order:
- Specify →
.github/sddp/workflows/specify-feature/WORKFLOW.md - Clarify →
.github/sddp/workflows/clarify-spec/WORKFLOW.md - Plan →
.github/sddp/workflows/plan-feature/WORKFLOW.md - Checklist →
.github/sddp/workflows/generate-checklist/WORKFLOW.md(looped until queue exhausted) - Tasks →
.github/sddp/workflows/generate-tasks/WORKFLOW.md - Analyze →
.github/sddp/workflows/analyze-compliance/WORKFLOW.md - Implement+QC →
.github/sddp/workflows/implement-qc-loop/WORKFLOW.md
When any sub-skill says Delegate, read the exact referenced sub-agent file at that point, not before, then perform the delegated task yourself.
AUTOPILOT = true for all phases. At every user interaction point, choose the recommended default and log the decision — never prompt the user.
Report progress at each phase boundary. Only halt for the conditions defined in the pipeline skill.
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.
- 11d ago First seen · 33 lines · 30 tokens per session scan A 2c89490d05c6
sddp-autopilot is a skill published in the GitHub repository attilaszasz/sdd-pilot (96 stars, last pushed 6d ago), licensed MIT. It adds 30 tokens to every session and 696 once invoked, about $0.0002 per session on Opus 5. 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-08-30.
Other skills, from other repositories
universal-live-check
Universal live-check framework for coding agents. Executes incremental, deterministic validation across all software domains (CLI, backend, frontend, mobile, embedded, libs). Change-type-aware (feat, fix, hotfix, refactor, migrate, docs). Triggers whenever an agent needs to validate code quality, run linting, perform…
code-review-hardening
Use this skill for rigorous, structured code review with a self-repair loop. Applies change-type-aware strategies (feat, fix, hotfix, refactor, migrate, docs). Findings are severity-classified, then auto-fixed where possible. Triggers on PR reviews, code review requests, or when reviewing any change set.
contextual-stewardship
Use this skill when the user makes a technical decision, establishes a new pattern, defines business rules, or explicitly asks to remember or save a guideline. Also use this skill when you are about to implement a feature, write code, plan an architecture, or make a technical decision - you MUST retrieve contextual…
project-guidelines-writer
Use this skill when the user wants repository guidance documents generated or refreshed, including AGENTS.md, CONTRIBUTING.md, STYLEGUIDE.md, TESTING.md, ARCHITECTURE.md, and SECURITY.md. It analyzes the repository, generates all six guideline files by default, prefers managed-section updates for existing files, and…
quality-grading
Use this skill to grade code, specifications, or design documents across four quality dimensions using a 1-5 scoring scale. In grade-and-fix mode, the skill auto-improves artifacts scoring below 5 without prompting. Invoke when you want consistent quality assessment on design, implementation, or specification with…
spec-driven-task-decomposer
Use this skill when approved requirements and design need to be decomposed into tasks.md for Phase 3 of a Spec-Driven change. It creates atomic, traceable implementation and testing tasks, validates the plan, and should not be used to design architecture or write implementation code.