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 Hmbown/Wizards-of-the-Ghosts --skill vicious-mockerygit clone --depth 1 https://github.com/Hmbown/Wizards-of-the-GhostsWrote 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/hmbown/wizards-of-the-ghosts/vicious-mockery)<a href="https://agentmods.dev/skills/hmbown/wizards-of-the-ghosts/vicious-mockery"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/vicious-mockery/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/hmbown/wizards-of-the-ghosts/vicious-mockery"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/vicious-mockery.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.00101 | $0.00789 |
| Opus 5.5 | $0.00040 | $0.00316 |
| Sonnet 5.5 | $0.00020 | $0.00158 |
| Haiku 4.5 | $0.00010 | $0.00079 |
Grade A, and why
vicious-mockery 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vicious Mockery
Deliver a critique so sharp it actually weakens the target's position.
What This Skill Does
The bard's cantrip that deals psychic damage through insults. In practice this is adversarial review — the art of finding and articulating exactly what is wrong with something in a way that is impossible to ignore. Unlike polite feedback that gets filed and forgotten, vicious mockery lands. It is the red-team report that makes the PM cancel the launch, the code review that makes the author delete the PR, the roast that makes the founder pivot. The damage is the point. In this grimoire, Vicious Mockery is treated as a metaphorical spell with a shipping-now delivery profile. Canonical reference input: Vicious Mockery (spell).
When To Use
- You need a brutally honest review that will actually change someone's mind, not a diplomatic sandwich.
- The target is a plan, proposal, design, or argument that needs its weaknesses surfaced without mercy.
- You want red-teaming, adversarial QA, or devil's advocate analysis that does not pull punches.
Prerequisites
- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.
Procedure
- Restate the target, the success condition, and any no-touch boundaries before taking action.
- Identify the target: the plan, argument, design, code, or proposal to critique.
- Find the real weaknesses — not cosmetic issues but structural flaws, bad assumptions, or hidden risks.
- Articulate each weakness in the most vivid, memorable, undeniable way possible.
- Rank by severity. Lead with the kill shot.
- Close with one constructive line — the mockery should wound, not kill. The goal is improvement.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A ranked list of weaknesses, each stated in one sharp sentence.
- The single most damaging critique, stated memorably enough to stick in a meeting.
- One constructive suggestion that survives the demolition.
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 · 69 lines · 101 tokens per session scan A ebacacfcdd79
vicious-mockery is a skill published in the GitHub repository Hmbown/Wizards-of-the-Ghosts (112 stars, last pushed 6mo ago), licensed CC0-1.0. It adds 101 tokens to every session and 789 once invoked, about $0.0004 per session on Opus 5.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
md-audit
Read-only code quality audit — scan the current working directory for common issues (bugs, dead code, security hotspots, missing error handling) and return a prioritised findings report. No files are edited. Use when asked to "audit the code", "quick audit", "find issues", "code scan", or "what's wrong with this…
resolve-review-pr
Review an existing fix PR using the audited repro and full diff, preserving branch and approval rules.
debug-plan
Create a systematic debugging plan for a bug report. Use when the user asks how to investigate a failure, regression, or unexpected behavior.
brutal-honesty-review
Unvarnished technical criticism combining Linus Torvalds' precision, Gordon Ramsay's standards, and James Bach's BS-detection. Use when code/tests need harsh reality checks, certification schemes smell fishy, or technical decisions lack rigor. No sugar-coating, just surgical truth about what's broken and why.
cocoreview
CocoReview — structured code review with six-severity findings vocabulary, progressive disclosure architecture, and universal anti-pattern baseline. Invoked via $review [file] [--complexity] [--security] [--architecture] [--language ].
reproduce
Reproduce a cloudflare/agents GitHub issue by scaffolding a minimal Agents/Worker project and deploying it to a temporary Cloudflare account, then report findings back on the issue.