Borrowing it
Nothing to install: this file belongs to re-cinq/wave. 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/re-cinq/wave/main/.agents/skills/wave-smoke-test/SKILL.mdgit clone --depth 1 https://github.com/re-cinq/waveWrote 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/re-cinq/wave/wave-smoke-test)<a href="https://agentmods.dev/skills/re-cinq/wave/wave-smoke-test"><img src="https://agentmods.dev/badge/skills/re-cinq/wave/wave-smoke-test/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/re-cinq/wave/wave-smoke-test"><img src="https://agentmods.dev/badge/skills/re-cinq/wave/wave-smoke-test.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.00039 | $0.00174 |
| Opus 5.5 | $0.00016 | $0.00070 |
| Sonnet 5.5 | $0.00008 | $0.00035 |
| Haiku 4.5 | $0.00004 | $0.00017 |
Grade A, and why
wave-smoke-test 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 Smoke Test Skill
This skill exists solely to verify that adapter-native skill provisioning works end-to-end across all four supported adapters (claude, opencode, gemini, codex).
Activation contract
When you activate this skill via your native skill tool, you MUST:
-
Acknowledge that you read this SKILL.md.
-
Emit the sentinel string on a line by itself, exactly:
SMOKE_TEST_OK_4f7a2b1c -
Stop. Do nothing else.
The Wave smoke-test pipelines look for that exact sentinel in your output. Any deviation fails the contract.
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 · 24 lines · 39 tokens per session scan A 8361ae4c12a0
wave-smoke-test is a skill published in the GitHub repository re-cinq/wave (23 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 174 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-30.
Other skills, from other repositories
backend
Backend development skill for microservices following Clean Architecture, CQRS with a transactional outbox, the repository/use-case pattern, and a Testing-Trophy strategy.
tdd-workflow
Test-Driven Development workflow for implementing features with tests first; enforces the two-commit audit trail (failing-test commit, then green commit) and shows-your-work verification for agent-driven work.
verification
Structured multi-phase verification of implementations before deployment, covering static analysis, testing, functional checks, security, and documentation.
verification-before-completion
Comprehensive five-level validation checklist that every agent must pass before declaring any task or work package complete.
interactive-live-testing
Drive Playwright against a running application step-by-step, screenshot, analyze, decide, act. Applies to any web frontend regardless of stack.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.