Borrowing it
Nothing to install: this file belongs to tatargabor/set-core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tatargabor/set-core/main/.claude/skills/set/wave-board/SKILL.mdgit clone --depth 1 https://github.com/tatargabor/set-coreWrote 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/tatargabor/set-core/wave-board)<a href="https://agentmods.dev/skills/tatargabor/set-core/wave-board"><img src="https://agentmods.dev/badge/skills/tatargabor/set-core/wave-board/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.
<a href="https://agentmods.dev/skills/tatargabor/set-core/wave-board"><img src="https://agentmods.dev/badge/skills/tatargabor/set-core/wave-board.svg" alt="Reviewed on agentmods" width="80" 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.00129 | $0.01705 |
| Opus 5.5 | $0.00052 | $0.00682 |
| Sonnet 5.5 | $0.00026 | $0.00341 |
| Haiku 4.5 | $0.00013 | $0.00170 |
Grade A, and why
set:wave-board 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 11d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wave board — set-wave-board
A process roadmap, not a product roadmap: which wave a job is in, which item is done, in
progress or blocked, and what is left. One job is one tracked file,
docs/waveboard/<job>.json, in the repository that runs the job, and one private Artifact page
that shows it live.
When to use it
Use a board when a job has several steps that outlive one session or run across several
projects: the status must survive a compact, a /clear, a second machine and a second person.
A three-step task done in one sitting does not need one; a todo list is enough there.
How the status stays true — three layers
- The job file — waves, items, and for each item the evidence that proves it.
sync, run by theset-hook-waveboardStop hook on every stop, whether or not you remembered — it derives status from evidence.- Your own report,
set-wave-board set <job> <item> <status>— the fast lane. Report every finished step with it, straight away. But evidence and the hook are the guarantee: where evidence speaks it overrides your report (adonewith unchecked task boxes comes back asdoing, andsetsays so). Onlyblockedandskippedsurvive evidence — they are human decisions.
Give every item evidence wherever one exists. An item without evidence is only as reliable as the last report.
| Evidence | Done when |
|---|---|
{"type":"openspec-tasks","path":"openspec/changes/<x>/tasks.md"} |
every box checked (some = doing, none = todo); also when only openspec/changes/archive/*-<x>/tasks.md exists |
{"type":"path-exists","path":"<repo-relative path>"} |
the path exists |
{"type":"commit","grep":"<pattern>"} |
git log --grep on HEAD finds a commit |
{"type":"project","project":"<registry name>","evidence":{...}} |
the nested evidence holds in that registered project |
Paths are relative to the repository root — never absolute; another project is named by its
set-core registry name and resolved per machine. A missing path or commit is not a verdict:
the status stays as it was (absence cannot tell "not yet" from "not on this machine"). A
project not registered on this machine is reported as UNRESOLVED and left alone.
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.
- 11d ago First seen · 118 lines · 129 tokens per session scan A 152902d7b1f7
set:wave-board is a skill published in the GitHub repository tatargabor/set-core (36 stars, last pushed 13d ago), licensed MIT. It adds 129 tokens to every session and 1,705 once invoked, about $0.0005 per session on Opus 5.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-10-09.
Other skills, from other repositories
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-init
Bootstrapping new Atmos projects with atmos init: built-in template catalog, differences from atmos scaffold generate, project record, and update-safe 3-way merge.
atmos-workflows
Workflow automation: native step types, multi-step workflows, parallel/matrix/wait/container/emulator steps, when: conditions (CEL), require/assert preconditions, output steps, retries, dependencies, and cross-component orchestration.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
atmos-imports
Atmos imports: local and remote stack imports, go-getter schemes, templated imports, import context, remote imports vs component source/vendoring, and private GitHub imports through github/sts.
squads-cli
Squads CLI — operate your squads through the loop; intent in, reviewed work out. TRIGGER when running squads, dispatching agents, triaging the inbox, reading/writing memory, recording feedback, or checking status/usage.