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-projectplangit 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-projectplan)<a href="https://agentmods.dev/skills/attilaszasz/sdd-pilot/sddp-projectplan"><img src="https://agentmods.dev/badge/skills/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/skills/attilaszasz/sdd-pilot/sddp-projectplan"><img src="https://agentmods.dev/badge/skills/attilaszasz/sdd-pilot/sddp-projectplan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.00214 |
| Opus 5 | $0.00015 | $0.00107 |
| Sonnet 5 | $0.00006 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00021 |
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 12d 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: [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.
Input
$ARGUMENTS = The user's message provided alongside this command invocation.
If the user provided no message, 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.
- 12d ago First seen · 18 lines · 31 tokens per session scan A 70269e293d04
sddp-projectplan is a skill published in the GitHub repository attilaszasz/sdd-pilot (96 stars, last pushed 7d ago), licensed MIT. It adds 31 tokens to every session and 214 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
spec-driven-task-implementer
Use this skill when an approved Spec-Driven change has reached Phase 4 and the user wants a task, phase, or full feature implemented from .specs/changes/ . It executes tasks in order, updates task status immediately, verifies each task before completion, and should not be used before implementation approval.
next
Phase 3 of the Tripod workflow, run repeatedly. Finds the first unchecked task in TASKS.md, implements it under the rules in CLAUDE.md, verifies its "Done when" condition, checks the box, and commits. Use when the user says "next task", "continue", "keep going", or invokes /tripod:next.
tasks
Phase 2 of the Tripod workflow. Reads SPEC.md and CLAUDE.md, then writes TASKS.md — an ordered list of small, scoped, verifiable tasks that implement the entire MVP. Use after the user has reviewed their spec, when they ask to "create tasks" or "break down the work", or when they invoke /tripod:tasks.
speckit-taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
speckit-converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
spk-run-verdict-capture
Set a Spec Kitty work-package review verdict through the deterministic event-log seam, so every agent harness records approve/reject the same way.