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 agentmods add skills/danweinerdev/claude-sdd-planner/setupnpx skills add danweinerdev/claude-sdd-planner --skill setupgit clone --depth 1 https://github.com/danweinerdev/claude-sdd-plannerWrote 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/danweinerdev/claude-sdd-planner/setup)<a href="https://agentmods.dev/skills/danweinerdev/claude-sdd-planner/setup"><img src="https://agentmods.dev/badge/skills/danweinerdev/claude-sdd-planner/setup.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 | $0.00048 | $0.01793 |
| Opus 5 | $0.00024 | $0.00897 |
| Sonnet 5 | $0.00010 | $0.00359 |
| Haiku 4.5 | $0.00005 | $0.00179 |
Grade A, and why
setup 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup — Configure a Directory for SDD Planner
Path Resolution
The plugin directory contains commands/, agents/, and shared/ as siblings. Find it by globbing for **/commands/research/SKILL.md in both the current directory and ~/.claude/plugins/cache/; if multiple versions match, sort them as semantic versions (like sort -V) and use the highest, then strip commands/research/SKILL.md from the match. Setup writes the config the other skills resolve from — shared/path-resolution.md defines how the planningRoot written here is later interpreted.
When to Use
When configuring a directory (an existing repo, a fresh git init, a Perforce workspace, or an empty directory) to work with the sdd-planner plugin. Idempotent and safe to re-run: overwrites planning-config.json only when the resolved planningRoot differs, overwrites launcher scripts, and creates only missing directories.
What setup does not do: resolve paths (user-given paths are stored verbatim — relative stays relative, absolute stays absolute), initialize a VCS, copy plugin files/templates/schemas into the target (the plugin reads its own files in place), write CLAUDE.md unprompted, or handle bare git repos (run it on a worktree instead).
Arguments
- target path — directory to configure (defaults to cwd). A non-path name is looked up in the current directory's
planning-config.local.jsonunderrepositories.<name>.path. - --planning-root
<path>— where planning artifacts live; stored as-given.
Process
1. Verify Provisioning — before any filesystem mutation
The plugin's skills and hooks all drive the sdd binary, so setup verifies it
first and stops the entire setup when it can't. This ordering is the
point: a half-configured repo whose hooks silently fail open is worse than a
repo setup refused to touch.
Run, with ${CLAUDE_PLUGIN_ROOT} set to the plugin directory:
sdd provision --plugin-root "${CLAUDE_PLUGIN_ROOT}"
This resolves a binary (plugin-root copy first, then PATH), admits it only
at or above the plugin's minSddVersion, and places or refreshes
${CLAUDE_PLUGIN_ROOT}/bin/sdd[.exe] on every run — including when the
resolved binary was already on PATH.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 130 lines · 48 tokens per session scan A deaa0fd5f40d
setup is a skill published in the GitHub repository danweinerdev/claude-sdd-planner (2 stars, last pushed 5d ago), licensed MIT. It adds 48 tokens to every session and 1,793 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-31.
Other skills, from other repositories
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
hns-workflow-ci-loop
Unified CI watch + auto-fix loop skill. Polls gh pr checks after /moai sync PR creation, classifies required vs auxiliary failures, attempts safe automated patches (max 3 iterations), and escalates semantic failures to the user. Use for CI loop workflow — NOT for general loop iteration patterns (see…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
hns-moaiadk-patterns
Skill "hns-moaiadk-patterns" from modu-ai/moai-adk, covering moai-adk-go domain patterns, architecture quick reference, key source paths, pipeline specialist delegation map and template-first build cycle.
moai-harness-learner
Harness learning subsystem coordinator. Produces Tier 4 auto-update proposal payloads consumed by the orchestrator (which surfaces them via AskUserQuestion) and orchestrates Apply/Rollback flows. Triggers when harness learning proposals are pending or learning lifecycle management is needed.
hns-oss-docs-readme-sync
README 4-file synchronization procedure for the oss-docs harness: Korean README.ko.md as primary source, en/ja/zh derivation, the shared language-switcher header contract, section-order parity checklist, and the manual verification recipe (no linter exists for READMEs). Loaded by the content-author and…