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 agentmods add skills/melodic-software/claude-code-plugins/wait-whatnpx skills add melodic-software/claude-code-plugins --skill wait-whatgit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWrote 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/melodic-software/claude-code-plugins/wait-what)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/wait-what"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/wait-what.svg" alt="Measured on agentmods" 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 | $0.00072 | $0.00564 |
| Opus 5 | $0.00036 | $0.00282 |
| Sonnet 5 | $0.00014 | $0.00113 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
wait-what 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 yesterday.
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
Wait. What?
Wait. I don't understand where you've got to here. Re-pitch that: back up as far as needed, give me the context I was missing, talk in ASD-STE100 Simplified Technical English (short sentences, one meaning per word, technical terms exact), and use the project's ubiquitous language. Read the nearest domain glossary or context map, per the project's own convention, when one exists; with none, plain technical English alone.
A declared species in this plugin: NOT a corrector
Every sibling corrector re-anchors a standing discipline through the
re-anchor/audit/correct loop. This skill is a one-shot, user-fired
communication repair: the human, the only party who can detect that a message
did not land, fires it, and the re-pitch IS the repair. It deliberately stays
this small: a skill that fights unclear output fails by growing, because the
model reads the volume, not the plea. Nearest siblings, for routing:
/discipline:tighten-your-output when the problem is too many words, and
/discipline:mind-your-maxims when the standing cooperative-communication
discipline itself needs re-anchoring; this skill repairs the one message that
lost its reader.
Boundaries
- Never model-invoked.
disable-model-invocation: trueis load-bearing: the model cannot detect that its reader stopped following, so an auto-fired re-pitch would be incoherent. - Re-pitch means re-ground, not compress. Full technical precision stays; the premise the reader was missing comes back. A re-pitch that is shorter and blunter, but no clearer, is the failure this skill exists to avoid.
- No glossary is a no-op, not an error. The vocabulary half degrades silently; the register and missing-context halves always apply.
- Excluded from batch sweeps. No
discipline-batchtier on purpose: a sweep must never fire a repair only the human can call for.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 44 lines · 72 tokens per session scan A 5eb1e1be5810
wait-what is a skill published in the GitHub repository melodic-software/claude-code-plugins (14 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 564 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
phpunit-unit-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
structuring-documentation
Use when writing, editing, auditing, splitting, or measuring Markdown documentation surfaces — README.md, AGENTS.md, CLAUDE.md, and docs/ siblings. Triggers include "is this doc too long", "split this README", "measure the docs", "where does this documentation belong", "audit the documentation", and any request to…
phpunit-integration-test-generation
Use this skill when the user asks to generate, write, or create integration tests for a Shopware 6 source class whose contract requires wired-up code — phrases like "generate integration tests for X", "write an integration test for this controller", "test this indexer", "create an integration test for the message…
phpunit-unit-test-writing
Use this skill when the user asks to write, generate, create, or add PHPUnit unit tests for a Shopware 6 source class — phrases like "write unit tests for X", "generate tests for ClassName", "create PHPUnit tests", "add test coverage", "test this class", "cover this with tests", "I need tests for", "unit test this"…
phpunit-migration-test-generation
Use this skill when the user asks to generate, write, or create migration tests for a Shopware 6 migration class — phrases like "generate migration tests", "write a migration test", "create migration test", "test this migration", "test Migration1234Foo". Analyzes the source migration's SQL operations to pick an…
phpunit-test-reconciling
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.