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 Wave-Engineering/mcp-server-wtf --skill wtf-imoutgit clone --depth 1 https://github.com/Wave-Engineering/mcp-server-wtfWrote 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/wave-engineering/mcp-server-wtf/wtf-imout)<a href="https://agentmods.dev/skills/wave-engineering/mcp-server-wtf/wtf-imout"><img src="https://agentmods.dev/badge/skills/wave-engineering/mcp-server-wtf/wtf-imout/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/wave-engineering/mcp-server-wtf/wtf-imout"><img src="https://agentmods.dev/badge/skills/wave-engineering/mcp-server-wtf/wtf-imout.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.00000 | $0.00210 |
| Opus 5 | $0.00000 | $0.00105 |
| Sonnet 5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
wtf-imout 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 8d 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
/wtf imout — Suspend Troubleshooting Session
Stop recording tool calls but preserve all captured data for later analysis.
Steps
-
Call the wtf_imout MCP tool:
- Fetch the tool if needed:
ToolSearchwith queryselect:mcp__wtf-server__wtf_imout - Call
mcp__wtf-server__wtf_imoutwith no arguments
- Fetch the tool if needed:
-
Parse the response and report to the user:
- If
ok: true→ "Recording suspended. Incident {incident_id} preserved for triage viawtf_happened." - If
ok: false→ "{message}" (e.g., "No active incident to suspend.")
- If
Important
- This does NOT delete captured data — it only stops future captures
- The suspended incident can still be viewed with
wtf_happened - Starting a new
/wtfsession will create a new incident (the suspended one remains archived)
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.
- 8d ago First seen · 20 lines · 0 tokens per session scan A 75a7ecaf383e
wtf-imout is a skill published in the GitHub repository Wave-Engineering/mcp-server-wtf (0 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 210 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.
Other skills, from other repositories
observations
List recent captured session observations (the Haiku-summarized voyage logs). Use when the user wants to see what Captain Memo has logged from past sessions.
bun-runtime-http
Covers Bun.serve, HTTP server configuration, routing, streaming responses, WebSockets, TLS/SSL, and middleware with Bun's native APIs.
bun-snippets-cli
CLI snippets and command-line automation recipes with Bun.
bun-runtime-templating
Covers HTML templating, JSX rendering, and server-side component rendering with Bun.
bun-guides-streams
Guides for working with WHATWG Streams, ReadableStream, WritableStream, and TransformStream in Bun.
bun-guides-write-file
Guides for writing files, appending data, atomic writes, and streaming file output in Bun.