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/validatenpx skills add danweinerdev/claude-sdd-planner --skill validategit 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/validate)<a href="https://agentmods.dev/skills/danweinerdev/claude-sdd-planner/validate"><img src="https://agentmods.dev/badge/skills/danweinerdev/claude-sdd-planner/validate.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.00046 | $0.01501 |
| Opus 5 | $0.00023 | $0.00750 |
| Sonnet 5 | $0.00009 | $0.00300 |
| Haiku 4.5 | $0.00005 | $0.00150 |
Grade A, and why
validate 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.
This is a copy
86% identical to sdd-validate — 15 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/validate — Validate SDD Artifacts
Path Resolution
The plugin directory contains commands/, agents/, scripts/, 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. Resolve the planning root per shared/path-resolution.md in the plugin directory. Also read shared/frontmatter-schema.md, shared/completion-evidence.md, shared/decision-log.md, and shared/review-artifacts.md — the conventions the validator enforces.
When to Use
Before implementation, before any completion transition, before handoff, or in CI. Read-only: validation never edits, moves, creates, or deletes artifacts and never changes a status — it reports exact findings for a lifecycle skill or user-authorized repair to address.
Process
1. Run the deterministic validator
From the target repository root:
sdd validate --format json
Pass --scope <planning-root-relative-path-or-artifact-name> when the user named a narrower scope. Scoped validation includes every discoverable artifact selected by that path/name and follows transitive explicit related links — a plan scope covers all plan-owned artifacts plus its governing related graph even when the scope names its README or one phase. Bare names that match multiple artifact roots are rejected as ambiguous; use the reported planning-root-relative path. JSON output lists the exact successfully parsed artifacts_in_scope; diagnostics for malformed files under the requested scope remain visible. Unresolved references remain diagnostics on the artifact that cites them; an existing but undiscoverable file is never claimed as validated.
If sdd is unavailable, report the error and stop rather than silently replacing deterministic checks with model judgment. Exit 0 means scripted checks passed, exit 1 means the JSON diagnostics are authoritative findings, and exit 2 means validation could not run. Never execute artifact-recorded evidence commands as part of validation.
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 · 62 lines · 46 tokens per session scan A 86a2223f7eb7
validate is a skill published in the GitHub repository danweinerdev/claude-sdd-planner (2 stars, last pushed 5d ago), licensed MIT. It adds 46 tokens to every session and 1,501 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to sdd-validate, differing in 15 lines, and is treated as a copy.
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…