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/decidenpx skills add danweinerdev/claude-sdd-planner --skill decidegit 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/decide)<a href="https://agentmods.dev/skills/danweinerdev/claude-sdd-planner/decide"><img src="https://agentmods.dev/badge/skills/danweinerdev/claude-sdd-planner/decide.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.01572 |
| Opus 5 | $0.00024 | $0.00786 |
| Sonnet 5 | $0.00010 | $0.00314 |
| Haiku 4.5 | $0.00005 | $0.00157 |
Grade C, and why
decide scanned grade C with 1 finding 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 today.
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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
0. An explicit `/decide` is the user asking for the entry — record it. But if the statement plainly fails the admission test (it restates what an artifact already says, or it's an event or one-off disposition), say so in This is a copy
91% identical to sdd-decide — 19 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/decide — Decision Ledger
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. Resolve the planning root (artifacts) per shared/path-resolution.md in the plugin directory.
When to Use
- Explicitly record a decision, concept definition, or answered design question as durable truth — a truth that must be findable without knowing which document to open, not a choice a spec or design already states (
shared/decision-log.md§ Capture, the admission test) - Look up what was decided about a topic ("what did we decide about auth?")
- Reconcile a collision — supersede an old decision with a new one
- Backfill a decision the automatic capture missed
- Audit ledger hygiene (
/decide check) — stale citations, missed collisions, malformed entries
The convention — entry schema, lifecycle rules, collision procedure — is defined in shared/decision-log.md (single source of truth). Read it before operating on the ledger.
Invocation
/decide <statement> # Record a decision (default subcommand)
/decide list [tag|scope] # List entries, optionally filtered
/decide search <term> # Find entries matching a term
/decide show D-NNNN # Show one entry with its body section, if any
/decide accept D-NNNN # Promote a proposed entry to accepted
/decide supersede D-NNNN # Replace an entry with a new decision
/decide check # Hygiene audit of the ledger and its citations
Process
0. Resolve the ledger
Resolve the ledger per shared/decision-log.md § Ledger location: <planning-root>/Decisions/decisions.md when the planning root is inside the repo; <repo-root>/DECISIONS.md when the planning root is external (decisions live with the repo they represent — resolve the repo via shared/path-resolution.md). If missing, create it from shared/templates/decision-log.md (and mkdir -p any needed directory) before proceeding.
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.
- today Changed 7498f1c7d6c8
- 4d ago First seen · 67 lines · 48 tokens per session scan C 734ad6d56b3e
decide is a skill published in the GitHub repository danweinerdev/claude-sdd-planner (2 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,572 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). It is 91% identical to sdd-decide, differing in 19 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…