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/debriefnpx skills add danweinerdev/claude-sdd-planner --skill debriefgit 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/debrief)<a href="https://agentmods.dev/skills/danweinerdev/claude-sdd-planner/debrief"><img src="https://agentmods.dev/badge/skills/danweinerdev/claude-sdd-planner/debrief.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.1 | $0.00029 | $0.01385 |
| Opus 5 | $0.00015 | $0.00692 |
| Sonnet 5 | $0.00006 | $0.00277 |
| Haiku 4.5 | $0.00003 | $0.00138 |
Grade A, and why
debrief 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 yesterday.
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-debrief — 17 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/debrief — After-Action Phase Notes
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) and target repository per shared/path-resolution.md in the plugin directory.
When to Use
When a plan phase has been completed (or substantially completed) and you want to capture what happened: decisions made, deviations from plan, lessons learned, and impact on future phases.
Process
-
Identify Target
- Scan
Plans/for plans whose README frontmatterstatusisactiveand that have in-progress or completed phases (debriefs happen during active work) - Ask which plan and phase to debrief (or infer from context)
- Read the phase document to understand what was planned
- Read the plan README for overall context
- Scan
-
Gather Information
- Review the phase's tasks and subtasks for completion status
- Read every task's
### Completion Evidence— an absent or pending section on acompletetask is a legacy evidence gap (shared/completion-evidence.md); report it in the debrief, never treat it as proof - Read related designs from
Designs/to identify deviations from intended architecture - Read related specs from
Specs/to assess requirements coverage - If more than ~3 related documents are involved, delegate the sweep to
sdd-planner:researcherinstead of reading them all yourself - Ask the user about:
- Key decisions made during implementation
- What deviated from the original plan or design
- Problems encountered and how they were resolved
- Insights to carry forward
-
Spot Skill Opportunities Review the phase for repeated actions that would benefit from being enshrined as a reusable skill. Look for:
- Manual sequences you (or the user) ran more than once — multi-step git workflows, recurring investigations, file-munging pipelines, check-lists that were applied by hand
- Repeated workflow sequences that always went together
- Codebase operations that lacked a helper/script and had to be redone in each task
- Checks or validations that should have been automated but were done mentally
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.
- yesterday Changed · +2 lines a0fb5414f1e6
- 5d ago First seen · 83 lines · 29 tokens per session scan A a2b1d2cfc5f8
debrief is a skill published in the GitHub repository danweinerdev/claude-sdd-planner (2 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 1,385 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to sdd-debrief, differing in 17 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…
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
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…
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.
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…