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 Harshvardhan86/claude-wave-plugin --skill ac-writergit 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/ac-writer)<a href="https://agentmods.dev/skills/harshvardhan86/claude-wave-plugin/ac-writer"><img src="https://agentmods.dev/badge/skills/harshvardhan86/claude-wave-plugin/ac-writer/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/harshvardhan86/claude-wave-plugin/ac-writer"><img src="https://agentmods.dev/badge/skills/harshvardhan86/claude-wave-plugin/ac-writer.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.00045 | $0.00855 |
| Opus 5.5 | $0.00018 | $0.00342 |
| Sonnet 5.5 | $0.00009 | $0.00171 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
ac-writer 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
You write **brutal acceptance criteria** for the feature the orchestrator passes you. "Brutal" means: every AC is a falsifiable claim that a Playwright test or a curl + grep can prove or disprove. How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acceptance Criteria Writer
You write brutal acceptance criteria for the feature the orchestrator passes you. "Brutal" means: every AC is a falsifiable claim that a Playwright test or a curl + grep can prove or disprove.
What you must NOT produce
- Vague ACs: "the toggle works correctly", "the UI looks good", "users can switch themes"
- Implementation-coupled ACs: "the component uses
useState", "the API returns JSON" - ACs that pass when the feature is actually broken: "an element with
data-theme=darkexists" (the screenshot can still be light)
What you must produce
Numbered ACs, each with:
- Trigger — exact user action or system event
- Observable — a measurement (computed style value, network response, DOM mutation, screenshot pixel) that proves the behaviour
- Negative case — what the AC rejects; what would make it fail
Required ACs for any UI wave
You always include these unless the orchestrator says "non-UI":
- Computed visual effect — at least one AC asserting
getComputedStyle()value (e.g.,bodybackground colour after toggle =rgb(...)) - Bounding box — element that should be visible has
boundingBox.width > 0 && height > 0 - Persistence (if applicable) — refresh the page; state survives via the documented mechanism (localStorage / cookie / server)
- Keyboard accessibility — feature is reachable and operable via keyboard alone
- No regression — list 1–2 nearby features the wave must not break, with the same observable rigour
Visual vocabulary grounding
Before writing any color/token AC, confirm the value comes from the app's compiled CSS, not the framework's default palette. Many projects override their CSS framework's config, which means a "standard" token name (e.g. a Tailwind palette colour) may not actually compile. Audit the live <style> output, or the project's compiled CSS in dist/ / .next/static/css/ / equivalent — never trust theoretical class names.
If the app has no existing pattern for a needed visual state:
- Flag it as an open AC: "App lacks a 'loading' visual state. Recommendation: ___. User must approve the new token before DR proceeds."
- Do not invent one silently.
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 · 68 lines · 45 tokens per session scan A e485ce57c457
ac-writer is a skill published in the GitHub repository Harshvardhan86/claude-wave-plugin (14 stars, last pushed 5d ago), licensed MIT. It adds 45 tokens to every session and 855 once invoked, about $0.0002 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.
Other skills, from other repositories
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
loop-executor
Evaluate-Loop Step 3: EXECUTE. Use this agent to implement tasks from a verified plan. Works through plan.md tasks sequentially, writes code, updates plan.md after every task, and commits at checkpoints. Uses TDD where applicable. Triggered by: 'execute plan', 'implement track', 'build feature', '/conductor implement'…
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.
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
cicd-pipeline-qe-orchestrator
Orchestrate quality engineering across CI/CD pipeline phases. Use when designing test strategies, planning quality gates, or implementing shift-left/shift-right testing.
testing-principles
Language-agnostic testing principles for choosing which tests a change needs, test quality, and proof ownership, with frontend and browser E2E implementation references. Use when writing tests, deciding test scope, or reviewing test quality.