Claude Code mod
wtf
Select text, run /wtf, and a side pane explains what it means in the context of this conversation, without adding anything to the conversation.
Install
/plugin marketplace add orangeJigglypuff/better-btw
/plugin install wtf@better-btwMods install like plugins. Run /reload-plugins or start a new session to load it.
What it can access
- Reach
- L2Writes or runs: drives Claude, reads the transcript, reads the selection, reads mod state, draws
- Draws in
PromptHintPane- Hooks
session.startcommand.runui.render
From a static scan of the mod's code by awesome-claude-code-mods. It shows what the code asks for, not a security review.
How Claude Code mods work
- A mod is a plugin with a JavaScript or TypeScript module that runs inside Claude Code (version 2.1.287 or later). It can draw panes beside the transcript, a band above the prompt, buttons and toasts, restyle the spinner and tool rows, and watch or rewrite tool calls and prompts.
- It installs like any plugin: add its marketplace with /plugin marketplace add owner/repo, then /plugin install name@marketplace.
- Check what a mod can reach before installing: it runs with your permissions. Reach goes from drawing only, to reading files, to writing files or running processes, to the network. Run claude plugin validate on a clone to list its hooks and calls without running it.
- Turn one off from the Installed tab in /plugin, or start Claude Code with --safe-mode to skip every customization for a session.
Details
- Repository
- orangeJigglypuff/better-btw
- Folder
wtf- Marketplace
better-btw- Author
- orangeJigglypuff
- License
- MIT
- Last updated
- 6 October 2026
- Listed in
- awesome-claude-code-mods
FAQ
What is wtf?
Select text, run /wtf, and a side pane explains what it means in the context of this conversation, without adding anything to the conversation. It is a mod for Claude Code, from orangeJigglypuff/better-btw on GitHub.
What can the wtf mod access?
Its widest reach is "writes or runs" (drives Claude, reads the transcript, reads the selection, reads mod state, draws). It draws in PromptHint, Pane. Like any mod, it runs with your permissions.
How do I install wtf?
Inside Claude Code (v2.1.287 or later), run /plugin marketplace add orangeJigglypuff/better-btw and then /plugin install wtf@better-btw.
More context & usage mods
workbench
Pigula1984/workbench
A set of mods that put live session data around the prompt box: statusbar (model, effort, mode, directory, branch, usage) and workflow (a dynamic workflow's steps under the prompt).
x48-usage
48X-Dev/claude-plugins
Saves Claude Code's 5-hour and weekly limits, context fill and session cost for the 48X AI Usage app.
windvane
20alexl/windvane
Babysits a long Claude Code session so you don't have to: the context fill is watched, the recorder drafts the checkpoint, compaction happens at the right point with the state banked and the work is resumed, the rules and the checkpoint ride inside the compacted conversation and every subagent's prompt, tool results are trimmed and secrets redacted at the door, project memory and rules are a tool call away, and a token ledger, a pane and a status segment show where the session stands.
yemeni-context-band
iyiob96/Context-Mod-Companion
Context-window band above the prompt with RTK token savings and a clickable pixel Yemeni companion whose mood follows how much context is left
widget-bridge
kirishimarisano-rgb/Mods-Claude-code-0-powerd-by-claude
Sends each local session's status (what Claude is doing, task progress, context and usage) to the Claude Widget desktop app on this computer, and takes its Stop button
zetetic-autopilot
cdeust/claude-mods
Automatic effort and model, and a quota that limits how many agents run, not how well one runs. Every request runs at the effort its grade calls for (zetetic-genius) and the main tool loop steps down the ladder. A subagent runs on the model its Agent call names, else the one its agent definition pins (read from the definition file, since agent.spawn carries only the call's), else the one the DESIGN block of its prompt names, else, for an inheriting type nobody designed, the rung of the dispatch table (hooks/dispatch-table.ts) for its task's class: one haiku completion grades the spawn prompt (routine, planned, bugfix, analysis, critical; a review or not), and the table gives model and effort (no haiku rung; a review runs on opus when complex, else on sonnet). A classifier that gives no class decides nothing: the spawn inherits and a POLICY row says why. Its effort is the Agent call's, else the one its definition sets, else DESIGN's, else the table's; an inheriting type the call gave a model runs every step at the effort of the turn's grade (main's spawns on a graded turn; a fork, a workflow agent or a teammate is never rewritten). No pressure, quota or context changes a model or an effort the orchestrator designed. Each spawn's requested, definition and decided model, what ran, the effort decided for its steps, the table's class and a short reason for each are kept per session. Quota pressure limits concurrency: the cap on subagents running at once falls from max_parallel_agents (5) at an empty five-hour window to 1 at quota_pressure_percent, and a spawn past it is refused with a message the orchestrator reads (wait for a running agent to finish). Only the main loop's own spawns, a fork of main included, are counted and refused: a subagent's nested spawn, a workflow script's agent() and a teammate are not. Main itself drops to sonnet under quota pressure, and doing implementation work in the main loop is warned about (POLICY row, toast), never blocked. A long streaming tool result is written whole to a file in the session's tool-results directory and the model reads a preview and the path (nothing is cut). Owns `phases`: the phase each loop is in (planning, analysis, design, implementation, verification, test, review, report), read off its tool calls or, for an agent, its type; on each run, the steps the stuck escalation raised (counted where each raised step landed, under enforce only); and the advisor calls of main with when they came. The tool loop of a phase the insights calibrated runs at that rung instead of medium (never above the request's grade). Starts in enforce; observe logs the decisions without applying them.
Browse the most popular Claude Code mods, all context & usage mods, or the skills and MCP server directories.