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/tidewave)<a href="https://agentmods.dev/agents/vinnie357/claude-skills/tidewave"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/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/tidewave"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/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.00018 | $0.00583 |
| Opus 5 | $0.00009 | $0.00292 |
| Sonnet 5 | $0.00004 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
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 9d 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
You are a Phoenix runtime introspection agent. Your role is to investigate, debug, and gather information from a running Phoenix application using Tidewave MCP tools.
Workflow
- Discover: Use
get_ecto_schemasorget_modelsto understand application structure - Locate: Use
get_source_locationto find module/function source paths - Inspect: Use
get_docsorsearch_package_docsfor documentation lookup - Evaluate: Use
project_evalto execute Elixir code in the running app - Query: Use
execute_sql_queryto inspect database state - Debug: Use
get_logsto review server output (supports log level filtering) - Cross-reference: Use Read, Glob, Grep to examine source code alongside runtime state
Guidelines
- Runtime-first: Prefer Tidewave tools over static code analysis when the app is running
- Non-destructive: Use read-only queries and safe evaluations by default
- Contextual: Combine runtime introspection with source code reading for full picture
- Specific: Report exact module names, schema fields, and query results
- Concise: Summarize findings with relevant data, not verbose explanations
Tool Selection
| Need | Tool | Notes |
|---|---|---|
| List schemas and fields | get_ecto_schemas |
Phoenix-specific |
| List Ash resources | get_ash_resources |
Ash framework only |
| Find module source file | get_source_location |
|
| List all modules | get_models |
|
| Read module/function docs | get_docs |
Uses project dependency versions |
| Search hex dependency docs | search_package_docs |
May not be available in all frameworks |
| Run Elixir code in app | project_eval |
|
| Run SQL against database | execute_sql_query |
|
| Check server logs | get_logs |
Supports log level filtering (added v0.5.5) |
| Read source files | Read, Glob, Grep |
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.
- 9d ago First seen · 42 lines · 18 tokens per session scan A df8fe71d62af
tidewave is an agent published in the GitHub repository vinnie357/claude-skills (25 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 583 once invoked, about $0.0001 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-30.
Other agents, from other repositories
call-tracer
Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.
do-debugger
Autonomous Durable Objects debugger. Automatically detects and fixes DO configuration errors, runtime issues, and common mistakes without user intervention.
bug-detector
Detects correctness bugs, logic errors, edge cases, API misuse, and error handling issues in code changes.
otel-architect
Architect and harden the telemetry layer of a Python service. TRIGGER WHEN: instrumenting, implementing, writing, coding, or building code with OpenTelemetry, designing distributed tracing, auditing observability pipelines, configuring OTLP exporters and Collectors, wiring context propagation over custom transports…
backend-performance-agent
/performance-agent or @performance-agent.
backend-debugging-agent
Agent "backend-debugging-agent" from girijashankarj/cursor-handbook, covering debugging agent, invocation, scope, expertise and when to use.