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/harshvardhan86/claude-wave-plugin/green-implnpx skills add Harshvardhan86/claude-wave-plugin --skill green-implgit clone --depth 1 https://github.com/Harshvardhan86/claude-wave-pluginWrote 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/harshvardhan86/claude-wave-plugin/green-impl)<a href="https://agentmods.dev/skills/harshvardhan86/claude-wave-plugin/green-impl"><img src="https://agentmods.dev/badge/skills/harshvardhan86/claude-wave-plugin/green-impl.svg" alt="Measured on agentmods" 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.00044 | $0.00937 |
| Opus 5 | $0.00022 | $0.00468 |
| Sonnet 5 | $0.00009 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
green-impl 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 5d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GREEN Implementation
You implement the minimum code to make the RED tests pass, and then you do something most agents skip: you start the live stack, run the full test suite against it, and take a screenshot. Only then do you hand off.
Why this skill exists
GREEN hand-off is never acceptable on tsc passes or build clean alone. That hand-off pattern produces piles of fake bugs in scanner phases. Verify-before-scan exists because real bugs hide behind builds that compile but apps that don't render.
Inputs
.wave/ac.md.wave/dr.md.wave/red.md(with RED-failing test output)
Procedure
1. Implement to the contract
- Use only tokens, components, and APIs documented in DR. If you find yourself wanting a token DR didn't audit, stop and surface it. Do not silently sub in a Tailwind default.
- Trace every config field end-to-end. If you add a config option, add the dispatch that reads it and a test that proves the runtime behaviour changes when the config changes. Catalog without dispatch is a lie.
- Keep the change surface minimal. No drive-by refactors, no "while I'm here" cleanup.
2. Make tests pass
Run the test suite. Iterate until RED tests pass and no existing tests break. If existing tests break, treat each as a P0 bug — fix the root cause, do not delete or skip the test.
3. Verify on a live stack — REQUIRED, NOT OPTIONAL
Before declaring done, you MUST:
a. Start the live stack. Run the project's actual dev/prod command (npm run dev, make run, docker compose up, whatever the project uses). Wait until the app is reachable.
b. Run the full phase test suite against the live stack. Not just the new tests — the full suite. Capture pass/fail.
c. Take a Playwright screenshot at every route the wave touches. Save to .wave/screenshots/green-<route>.png. Open the screenshot yourself and inspect it — does the visual match the DR mockup?
d. If a screenshot shows a visual bug, you fix it directly, in this same skill, in one edit pass. Do not dispatch another agent for a failure mode you already observed. Re-run the suite, re-screenshot.
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.
- 5d ago First seen · 76 lines · 44 tokens per session scan A b7410dcd03ca
green-impl is a skill published in the GitHub repository Harshvardhan86/claude-wave-plugin (8 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 937 once invoked, about $0.0002 per session on Opus 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
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the failing test first and watch it fail for the right reason.
test-web-ui
Automated web QA skill: analyzes a website or project, generates end-user use cases, derives a structured test plan, executes tests via Playwright browser automation, and produces a full HTML/Markdown QA report with screenshots and pass/fail results. TRIGGER this skill whenever the user asks to: test a website, run QA…
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
broken-link-checker
Scans a website to find broken links (404s, 500s). Crawls internal pages, identifies broken outbound links, and reports source pages for easy fixing. Use this when the user asks to "check for broken links", "find 404s", "audit my links", or "is my site healthy".
preview-screens
Use when the user wants to preview generated screens in a browser without starting Metro / a simulator — for example after /create-mobile-app finishes or after /edit-app regenerates a screen.