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/alfredoperez/sdd/implementnpx skills add alfredoperez/sdd --skill implementgit clone --depth 1 https://github.com/alfredoperez/sddWhat 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.00024 | $0.06085 |
| Opus 5 | $0.00012 | $0.03043 |
| Sonnet 5 | $0.00005 | $0.01217 |
| Haiku 4.5 | $0.00002 | $0.00609 |
Grade A, and why
sdd:implement 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 2d 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 — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shared Instructions
- Event Journal — append context updates to a per-spec write-ahead log; a single drain script materializes them into
.spec-context.json - Transition Logging — transition entry shape and millisecond
atprecision (the drainer materializes one transition per journal event) - Hook Execution — run user-configured hooks at supported pipeline points
- Branch Creation — optional feature-branch creation driven by
.sdd.jsonbranchStage - Layered Context — Layer 2 → Layer 1 delta sync at CP3 (Step 7b)
Context writes: journal + drain
This skill does not read-merge-write .spec-context.json on every task.
Per event-journal, each context
update is a one-line append to specs/{NNN}-{slug}/.spec-context.events.jsonl
(cheap; no read, no merge), and a single drain materializes the journal into
.spec-context.json at the boundaries called out below.
- On entry, read
drainedSeqfrom.spec-context.json(default 0) and the last journal line'sseq(default 0); set your run counter to the max. Each append increments it by 1. Each append carriesat(ms precision viadate -u +%Y-%m-%dT%H:%M:%S.%3NZ), the currentstep/substep, and thefrom(prior step+substep) — the drainer turns each event into exactly one transition. - To drain, run:
Drain at: Context Recovery (first), every ~3 solo tasks and before yielding the turn, each parallel-group end, before each checkpoint display (CP1/CP2/CP3), and beforepython3 lib/scripts/drain-spec-context.py specs/{NNN}-{slug}/git addin Steps 8 and 8b. The drainer is idempotent.
Steps
1. Load
If $ARGUMENTS is provided, use specs/{$ARGUMENTS}/ as the target directory.
Otherwise, find the most recently modified directory under specs/ that contains tasks.md.
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.
- 2d ago First seen · 442 lines · 24 tokens per session scan A b32c881bc9e2
sdd:implement is a skill published in the GitHub repository alfredoperez/sdd (2 stars, last pushed 11d ago), licensed MIT. It adds 24 tokens to every session and 6,085 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…