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 stinking-cloudgit 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/stinking-cloud)<a href="https://agentmods.dev/skills/hmbown/wizards-of-the-ghosts/stinking-cloud"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/stinking-cloud/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/stinking-cloud"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/stinking-cloud.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.00104 | $0.00805 |
| Opus 5 | $0.00052 | $0.00402 |
| Sonnet 5 | $0.00021 | $0.00161 |
| Haiku 4.5 | $0.00010 | $0.00081 |
Grade A, and why
stinking-cloud 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 9d 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.
Stinking Cloud
Make an area inhospitable without destroying it.
What This Skill Does
In D&D, Stinking Cloud fills an area with nauseating gas — creatures inside are incapacitated but the terrain itself is undamaged. The real-world version is area denial: making a zone, endpoint, or resource unusable to unwanted traffic without permanently destroying or modifying it. Rate limiting, IP-range blocks, honeypots, tarpits, geographic restrictions. Stinking Cloud is defensive — it protects a perimeter by making the area inside it miserable for intruders while leaving the underlying infrastructure intact. In this grimoire, Stinking Cloud is treated as a metaphorical spell with a shipping-now delivery profile. Canonical reference input: Stinking Cloud (spell).
When To Use
- You need to deter access to a resource, endpoint, or zone without destroying it.
- Defensive measures should slow, frustrate, or redirect unwanted traffic rather than block it outright.
- You want to set up a honeypot, tarpit, or deterrent zone that wastes attackers' time and resources.
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.
- Define the area to deny: which endpoints, IP ranges, geographic zones, or resources.
- Choose the deterrent mechanism: rate limiting, tarpitting, CAPTCHA walls, honeypots, or access throttling.
- Deploy the deterrent and verify it affects only the intended zone.
- Monitor for legitimate traffic caught in the cloud and create bypass mechanisms if needed.
- Set review criteria for when the cloud should be lifted or the perimeter adjusted.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A deployed area-denial mechanism with clear boundaries.
- Monitoring for false positives: legitimate users caught in the deterrent zone.
- A review schedule for adjusting or lifting the deterrent.
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.
- 9d ago First seen · 69 lines · 104 tokens per session scan A b6c0701fdc76
stinking-cloud is a skill published in the GitHub repository Hmbown/Wizards-of-the-Ghosts (107 stars, last pushed 5mo ago), licensed CC0-1.0. It adds 104 tokens to every session and 805 once invoked, about $0.0005 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
n8n-workflows
Use when n8n workflow automation — nodes, triggers, expressions, credentials, webhooks, error handling. Use when working with n8n workflows.
pipedream-workflows
Use when pipedream serverless workflows — triggers, code steps, pre-built actions, data stores, HTTP. Use when working with pipedream workflows.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
devex-sdk-design
Developer experience (DX) engineering, SDK design patterns, API ergonomics, CLI tooling design, documentation-driven development, and developer onboarding. Use when designing SDKs, improving API ergonomics, building developer tools, or creating developer documentation.
api-design
REST API contract designer and reviewer. ALWAYS use when designing new endpoints, reviewing existing API contracts, planning API versioning, or standardizing error models. Covers resource modeling (URL/naming), HTTP method semantics, status code selection, error model consistency, pagination/filtering/sorting…
kafka-event-driven-design
Kafka event-driven architecture designer and reviewer, at the application/client layer. ALWAYS use when designing, reviewing, or troubleshooting how a service produces or consumes Kafka events — topic and partition-key design, producer and consumer client configuration, consumer group topology, event schema definition…