agentmods.dev

wave-spec

wave-spec is a skill for Claude Code, Codex from dimkurilo/opencode-skills. It costs 155 tokens per session (15,378 once invoked), scanned A, original, MIT.

A planning workflow for multi-day or multi-session projects. It creates shared specification, plan, worker-brief, status, and handoff files in the repository before work begins.

In plain words
What is it for?
Use it to plan development, content, translations, site rebuilds, or other one-to-three-week projects before execution.
Why use it?
It prevents a longer project from starting without an agreed plan and makes progress easier to resume across sessions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md; mentions Codex; mentions OpenCode.

not rated 7repo 2mo ago A scan 155 tokens original MIT

Good fit Use it to plan development, content, translations, site rebuilds, or other one-to-three-week projects before execution.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dimkurilo/opencode-skills/wave-spec
View source ↗ dimkurilo/opencode-skills
Install

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.

Any agent
npx skills add dimkurilo/opencode-skills --skill wave-spec
Clone the repo
git clone --depth 1 https://github.com/dimkurilo/opencode-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for wave-spec

README.md
[![agentmods](https://agentmods.dev/badge/skills/dimkurilo/opencode-skills/wave-spec/github.svg)](https://agentmods.dev/skills/dimkurilo/opencode-skills/wave-spec)
Your own site
<a href="https://agentmods.dev/skills/dimkurilo/opencode-skills/wave-spec"><img src="https://agentmods.dev/badge/skills/dimkurilo/opencode-skills/wave-spec/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for wave-spec

Your own site · 80×15
<a href="https://agentmods.dev/skills/dimkurilo/opencode-skills/wave-spec"><img src="https://agentmods.dev/badge/skills/dimkurilo/opencode-skills/wave-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 155 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 15,378 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00155 $0.15378
Opus 5.5 $0.00062 $0.06151
Sonnet 5.5 $0.00031 $0.03076
Haiku 4.5 $0.00015 $0.01538

Measured 2mo ago against content hash 9a0c94e256a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo ago.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/test_update_review_packet.py, scripts/update_review_packet.py, scripts/verify-handoff-payload.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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) или проверяемый факт; проза — только если команды нет.
skills/wave-spec/SKILL.md · 777 lines

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

Read the full file on GitHub · 777 lines

Files

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.

Changes

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.

  1. 2mo ago First seen · 777 lines · 155 tokens per session scan A 9a0c94e256a8

Subscribe to this mod's changes

wave-spec is a skill published in the GitHub repository dimkurilo/opencode-skills (7 stars, last pushed 2mo ago), licensed MIT. It adds 155 tokens to every session and 15,378 once invoked, about $0.0006 per session on Opus 5.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.

Planning
Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens