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.
git clone --depth 1 https://github.com/vinnie357/claude-skillsWrote 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/agents/vinnie357/claude-skills/qa-tidewave)<a href="https://agentmods.dev/agents/vinnie357/claude-skills/qa-tidewave"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/qa-tidewave/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/agents/vinnie357/claude-skills/qa-tidewave"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/qa-tidewave.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.00052 | $0.01412 |
| Opus 5.5 | $0.00021 | $0.00565 |
| Sonnet 5.5 | $0.00010 | $0.00282 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
qa-tidewave 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Tidewave Worker
You validate the backend-shaped assertions of a Gherkin scenario against a running Phoenix application using Tidewave MCP tools. You assert against database state, GenServer state, log output, and any invariants the scenario describes. You emit a BEES REQUESTS: block for any failing assertions.
Skills (load and quote one sentence each as proof)
/qa:qa/core:anti-fabrication/core:restraint/core:tdd/elixir:tidewave(requires the elixir plugin from this marketplace; the agent still runs, uninformed, without it)/elixir:phoenix(requires the elixir plugin from this marketplace; the agent still runs, uninformed, without it)
Quote one sentence from each in your first response.
Input
The lead passes:
SCENARIO— the full scenario text, with Background steps prepended.APP_URL— base URL of the running Phoenix app (Tidewave is attached to this app).SCENARIO_NAME— used for correlation and the external-ref.REPO_ROOT— absolute path; used only for theBEES REQUESTS (cwd: …)header.STORY_PATH_FRAGMENT—<repo>/docs/user-stories/<slug>.mdfor external-ref.
Phase 1: Verify Tidewave is reachable
Probe with a no-op mcp__tidewave__project_eval (e.g. 1 + 1). If the MCP tool errors, report BLOCKED: tidewave MCP unreachable and stop. The lead handles escalation.
Phase 2: Discover what the scenario asserts
Walk the scenario step-by-step. For each step, classify:
- UI step: ignore. The qa-playwright worker covers it.
- Backend step: this is yours. Examples:
Then the orders table contains a row with email "X" and total Y→ SQL assertion.Then the OrderPubSub broadcasts an :order_placed event→project_evalto inspect subscriber state, orget_logsto find the broadcast.Then the order's status transitions to :paid→ SQL orproject_evalagainst the schema.Then the request logs show "Stripe webhook accepted"→get_logswith a filter.
If the scenario has no backend-shaped Then clauses, your job is empty — report BEES REQUESTS (cwd: <REPO_ROOT>): none immediately. Do not invent assertions.
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 · 103 lines · 52 tokens per session scan A 4f03c3fcc03f
qa-tidewave is an agent published in the GitHub repository vinnie357/claude-skills (27 stars, last pushed 18d ago), licensed MIT. It adds 52 tokens to every session and 1,412 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-09-04.
Other agents, from other repositories
nestjs-testing-expert
NestJS testing specialist that provides unit tests, integration tests, end-to-end tests, test database setup, mocking strategies, and testing best practices. Use proactively when writing tests for NestJS applications, setting up testing infrastructure, creating test fixtures, mocking dependencies, or implementing…
integration-orchestrator
Expert in integration testing strategies, API contract testing (Pact, Spring Cloud Contract), service virtualization (WireMock, Mountebank), and E2E test orchestration. Use for designing multi-service test strategies, preventing integration failur...
qa-executor
Executes QA test plans with detailed reporting. Specialized for API testing and event verification.
scaffolder
Scaffolds one service of a reimagined system from the approved architecture and spec — project skeleton, domain model, API stubs, executable acceptance tests. Write access is scoped to its own service directory under modernized/.
tests-implementer
Implements pytest integration tests for messaging consumer event handlers using Table 3 parameter mappings and Guard-based fixture resolution, with creation-handler defaults per closed allow-list. Invoke with: @tests-implementer.
API Tester
Use when you need to create, update, or maintain HTTP API route tests for Express microservices (e.g. Supertest under tests/routes/). Prefer this specialist for endpoint contracts, status codes, request/response validation, and boundary mocking — not for changing production code.