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 etherealnessgit 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/etherealness)<a href="https://agentmods.dev/skills/hmbown/wizards-of-the-ghosts/etherealness"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/etherealness/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/etherealness"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/etherealness.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.00059 | $0.00928 |
| Opus 5 | $0.00030 | $0.00464 |
| Sonnet 5 | $0.00012 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
etherealness 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Etherealness
Walk through the walls of a system without leaving fingerprints.
What This Skill Does
Etherealness is observational only. It answers "what is happening?" or "what would happen?" without changing anything. The system under study continues normally; you add a ghost layer that watches, mirrors, or dry-runs without becoming part of the live mutation path. In this grimoire, Etherealness is treated as a metaphorical spell with a prototype delivery profile. Canonical reference input: Etherealness (spell).
When To Use
- You need to observe production-like behavior without writing to the live system.
- A dry run, shadow deployment, or mirrored environment would answer the question more safely than direct experimentation.
- You want to inspect effects first and decide later whether crossing fully into action is justified.
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 least invasive observation surface that still answers the question. Prefer: existing metrics/logs → read replicas → shadow deployments → mirrored traffic. Escalate invasiveness only when necessary.
- Define the trust boundary. Explicitly state what the ghost view can prove and what it cannot. Dry runs don't capture live contention. Read replicas may lag. Mirrored traffic at 1% doesn't prove behavior at 100%.
- Return three deliverables:
- The observation setup plan (what to deploy, where, how to connect)
- Findings you can safely gather before acting
- A caveat list: what ghost mode cannot prove and what requires real execution to validate
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A read-only or shadow-observation setup plan.
- A list of findings you can gather safely before acting.
- A caveat list for what ghost mode cannot prove.
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 · 75 lines · 59 tokens per session scan A c3ee80b238bd
etherealness 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 59 tokens to every session and 928 once invoked, about $0.0003 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
agent-creator
Meta-agent for creating new custom agents, skills, and MCP integrations. Expert in agent design, MCP development, skill architecture, and rapid prototyping. Activate on 'create agent', 'new skill', 'MCP server', 'custom tool', 'agent design'. NOT for using existing agents (invoke them directly), general coding (use…
code-research
Use when produce structured understanding of unfamiliar codebases — architecture, data flows, dependencies, and conventions. Use when joining a new project, tracing feature implementations, or mapping system architecture.
crewai-agents
Use when crewAI multi-agent orchestration — agents, tasks, crews, tools, memory, delegation. Use when working with crewai agents.
code-agent
Use when implementing features from specs — reads requirements, writes code with tests, iterates until verification passes.
deploy-agent
Use when ship code through controlled pipeline with verification gates and rollback plans.
planning-agent
Use when decompose complex tasks into executable steps with dependencies, risk assessment, and verification criteria.