A flight recorder for troubleshooting incidents: sessions that capture observations, theories, and corrective actions while a problem is investigated.

Use it to start a new incident, optionally title it, and keep a running record of findings and attempted fixes.

It preserves the investigation and archives the previous incident, so important reasoning is not lost between troubleshooting sessions.

wtf — Skill for Claude Code and Codex by Wave-Engineering

Install

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.

Any agent

npx skills add Wave-Engineering/mcp-server-wtf --skill wtf

Clone the repo

git clone --depth 1 https://github.com/Wave-Engineering/mcp-server-wtf

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/wave-engineering/mcp-server-wtf/wtf/github.svg)](https://agentmods.dev/skills/wave-engineering/mcp-server-wtf/wtf)

Your own site

<a href="https://agentmods.dev/skills/wave-engineering/mcp-server-wtf/wtf"><img src="https://agentmods.dev/badge/skills/wave-engineering/mcp-server-wtf/wtf/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/wave-engineering/mcp-server-wtf/wtf"><img src="https://agentmods.dev/badge/skills/wave-engineering/mcp-server-wtf/wtf.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 524 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.00524
Opus 5.5	$0.00000	$0.00210
Sonnet 5.5	$0.00000	$0.00105
Haiku 4.5	$0.00000	$0.00052

Measured 1mo ago against content hash bca5220298c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wtf 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.

skills/wtf/SKILL.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/wtf — Start a Troubleshooting Session

Launch the WTF flight recorder for a new troubleshooting incident. Archives any prior incident, prompts for an optional title, then puts Claude into flight recorder mode where significant observations, theories, and corrective actions are journaled automatically.

Resolve Intent

Parse the invocation arguments:

No arguments — start a new troubleshooting session (default behavior).
record <text> — shorthand for /wtf now <text>. Route directly to the /wtf now skill with the provided text, then stop.

Steps

1. Archive prior incident

Call the wtf_freshell MCP tool with no arguments. This archives any currently active incident and creates a fresh one.

2. Prompt for incident title

Ask the user:

What are you troubleshooting? (optional — press Enter to skip)

If the user provides a title, call wtf_freshell again with { "title": "<user's title>" } to set the title on the newly created incident.

Wait for the user's response before proceeding.

3. Confirm and activate flight recorder mode

Tell the user the session is active, then follow these behavioral instructions for the remainder of the conversation:

You are now in WTF flight recorder mode. A background journal is capturing every tool call automatically. In addition to that automatic capture, you should:

Call wtf_now with gen_type: "crafted" and action_type: "breadcrumb" when you observe something diagnostically significant
Call wtf_now with gen_type: "crafted" and action_type: "theory" when you form a hypothesis about the root cause
Call wtf_now with gen_type: "crafted" and action_type: "action" when you take a corrective action (not exploratory commands)

Bias toward recording. When in doubt, record it. A noisy journal can be distilled; a silent journal cannot be recovered.

At any time, the user may call wtf_happened to see the current timeline, or /wtf now to add their own observations.

Read the full file on GitHub · 64 lines

Changes

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 · 64 lines · 0 tokens per session scan A bca5220298c5

Subscribe to this mod's changes

wtf is a skill published in the GitHub repository Wave-Engineering/mcp-server-wtf (0 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 524 tokens. 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.

Claude Code Debugging Flight Recorder bun incident-response mcp mcp-server

doctor

Health probe across the worker, embedder, summarizer, queue, vector index, schema, cross-AI wiring and plugin install (cache and live versions). Use when the user types /captain-memo:doctor or when something seems wrong.

kalinbogatzevski/captain-memo · 52 tokens

troubleshoot

Diagnose and fix claude-mem installation issues. Checks worker status, database integrity, service health, dependencies, and provides automated fixes for common problems.

CHANGGELY/claude_codex_gemini_mem · 35 tokens

api-linter

MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.

cyanheads/openstreetmap-mcp-server · 86 tokens

wtf