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/dimkurilo/opencode-skills/wave-specnpx skills add dimkurilo/opencode-skills --skill wave-specgit clone --depth 1 https://github.com/dimkurilo/opencode-skillsWhat 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.00155 | $0.15378 |
| Opus 5 | $0.00077 | $0.07689 |
| Sonnet 5 | $0.00031 | $0.03076 |
| Haiku 4.5 | $0.00015 | $0.01538 |
Grade A, and why
wave-spec scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `done_when` = **исполняемая команда** (grep/test/curl) или проверяемый факт; проза — только если команды нет. How it starts
The opening of the file, as written. The whole thing — 777 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wave-spec
Method: same as vv-opencode (vv-spec → vv-plan → approve → exec), but portable:
structured XML artifacts in the repo, any orchestrator CLI.
You (the agent) execute this skill. The user does not need to invent the pipeline.
Positioning (identity): wave-spec is a universal plan-gate + lifecycle skill for 1–3 week product waves across any domain — development, content, skill-port, translation, orchestration, site rebuild. It is NOT an SEO costume and NOT gsd-core / gsd-coordinator / vv-opencode runtime — no agentic dispatch, no worktree groups, no structured handoff beyond project-local SESSION_HANDOFF. The lifecycle gates below are the contract; full identity and boundaries in Positioning.
TL;DR (minimum path — 5 минут)
wave-spec = план-гейт. Пишет в waves/<date>-<slug>/: INTENT → SPEC.xml → PLAN.xml → approve → exec → STATUS/handoff. Не для однострочных правок (для них mode=quick).
Прочитай только: Modes → Hard gate → Pipeline шаги 0–5 → approve. Остальное (NEXT_SESSION/Linear) — по мере возникновения; LAUNCH.md обязателен для wave/program до dispatch (см. Шаг 6.0).
Лестница обучения: Волна 1 = mode=quick (весь цикл за 1 сессию) → Волна 2 = полный wave + 1 review → Волна 3+ = multi-model-orchestration. Учись деланием, не чтением.
Роутер: новый проект → project-bootstrap · план спринта → wave-spec · 2+ модели → multi-model-orchestration.
Modes
| Mode | Trigger | Output |
|---|---|---|
quick |
Trivial / пет-проект: ≤1 файл, ≤30 мин, no deploy | INTENT 5 строк → SPEC 10 строк → approve → apply → archive (1 файл, без LAUNCH/NEXT_SESSION/Linear) |
wave (default) |
One sprint 2–7 days / one theme | waves/<date>-<slug>/… |
task |
Single atomic task inside approved wave | waves/.../tasks/TNN-*.xml + worker brief |
program |
Multi-wave portfolio (fidelity port, book translation, site rebuild) — редко; см. references/program-maps.md |
roadmap/PROGRAM_SPEC.xml + roadmap/PROGRAM_PLAN.xml |
What ships with it
28 files 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.
- assets/hero-dark.svg 2.4 KB
- assets/hero-light.svg 2.4 KB
- assets/templates/ASSUMPTIONS.md.tmpl 858 B
- assets/templates/fix-round-brief.md.tmpl 2.2 KB
- assets/templates/INTENT.md.tmpl 543 B
- assets/templates/iteration-handoff.md.tmpl 1.5 KB
- assets/templates/LAUNCH.md.tmpl 3.8 KB
- assets/templates/linear-workflow.md.tmpl 1.1 KB
- assets/templates/NEXT_SESSION_ITER.md.tmpl 9.2 KB
- assets/templates/NEXT_SESSION.md.tmpl 1.3 KB
- assets/templates/PLAN.xml.tmpl 3.1 KB
- assets/templates/premortem-brief.md.tmpl 4.2 KB
- assets/templates/quick-spec.md.tmpl 2.1 KB
- assets/templates/re-dispatch-brief.md.tmpl 4.9 KB
- assets/templates/review-synthesis.md.tmpl 5.4 KB
- assets/templates/SPEC.xml.tmpl 4.0 KB
- assets/templates/STATUS.md.tmpl 1.1 KB
- assets/templates/worker-brief.md.tmpl 6.2 KB
- README.md 8.8 KB
- README.ru.md 11 KB
- references/glossary.md 6.4 KB
- references/program-maps.md 8.6 KB
- references/vv-portability.md 3.5 KB
- references/worked-examples.md 5.5 KB
- scripts/test_update_review_packet.py 17 KB runs code
- scripts/update_review_packet.py 19 KB runs code
- scripts/verify-handoff-payload.sh 14 KB runs code
- scripts/verify-spec.sh 10 KB runs code
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 · 777 lines · 155 tokens per session scan A 9a0c94e256a8
wave-spec is a skill published in the GitHub repository dimkurilo/opencode-skills (6 stars, last pushed 20d ago), licensed MIT. It adds 155 tokens to every session and 15,378 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…