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 skills add Maless88/Roadboard --skill wave-closegit clone --depth 1 https://github.com/Maless88/RoadboardWrote 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/maless88/roadboard/wave-close)<a href="https://agentmods.dev/skills/maless88/roadboard/wave-close"><img src="https://agentmods.dev/badge/skills/maless88/roadboard/wave-close/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/maless88/roadboard/wave-close"><img src="https://agentmods.dev/badge/skills/maless88/roadboard/wave-close.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.00057 | $0.00317 |
| Opus 5.5 | $0.00023 | $0.00127 |
| Sonnet 5.5 | $0.00011 | $0.00063 |
| Haiku 4.5 | $0.00006 | $0.00032 |
Grade A, and why
wave-close 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 1mo 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.
What it actually says
Wave close checklist
Before declaring a wave complete in RoadBoard, in this order:
- All wave prompts are in
tasks/done/— verify the filesystem. Any prompt still intasks/run/ortasks/todo/→ the wave is NOT complete. - Run
/security-review(MANDATORY) on the code delivered in the wave. The wave is not closed until the review completes and every Critical/High finding is resolved or explicitly deferred with a written rationale. If Critical/High remain → openfix-prompts before closing. - Update
CHANGELOG.md— add the wave's deliverables under[Unreleased](Keep a Changelog sections: Added/Changed/Fixed/Removed/Deprecated/Security). - Flip the wave checkboxes in
PLAN.md— only after steps 1–3. - Update the wave status in RoadBoard —
mcp__roadboard__update_phase(RoadBoard is the source of truth; the phase state lives there, not in side files).
No wave closes without the security review. Never mark a phase complete in RoadBoard without having actually done steps 1–4.
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.
- 1mo ago First seen · 17 lines · 57 tokens per session scan A 328a561738d4
wave-close is a skill published in the GitHub repository Maless88/Roadboard (3 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 317 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
change-management
Create and transition ServiceNow change requests (normal/standard/emergency), change tasks, affected CIs, approval routing, CAB scheduling, and conflict detection across maintenance windows.
sla-management
Configure ServiceNow SLAs — contractsla definitions with start/stop/pause/cancel conditions, tasksla status checks, breach escalation, business-hours schedules, and compliance-rate aggregation.
vendor-management
Manage ServiceNow vendors and contracts — corecompany vendor records, astcontract with renewal alerts, astcontractsla performance tracking, vendorriskassessment scoring, and vendor scorecards.
virtual-agent
Build ServiceNow Virtual Agent — syscstopic conversations, topic blocks (text/prompt/script/decision/handoff), NLU utterances and custom entities, quick replies, and KB/incident integration scripts.
agile-development
ServiceNow Agile Development 2.0 — the rmteam → rmsprint → rmstory → rmepic model, the state and point values ServiceNow actually accepts, how a story is attached to a sprint, and the reporting tools (board, burndown, velocity, capacity, standup, retrospective).
coordinate
Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.