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 mordenkainen-s-swordgit 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/mordenkainen-s-sword)<a href="https://agentmods.dev/skills/hmbown/wizards-of-the-ghosts/mordenkainen-s-sword"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/mordenkainen-s-sword/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/mordenkainen-s-sword"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/mordenkainen-s-sword.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.00066 | $0.00673 |
| Opus 5 | $0.00033 | $0.00336 |
| Sonnet 5 | $0.00013 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
mordenkainen-s-sword 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mordenkainen’s Sword
Summon a standing process that keeps cutting through one job until dismissed.
What This Skill Does
Use this spell when you need an autonomous tool with a narrow mandate: a daemon, scheduled worker, watcher, or persistent background agent that repeatedly executes one precise task. It is prototype territory because the hard part is lifecycle control, observability, and safe cancellation, not the single action itself. In this grimoire, Mordenkainen’s Sword is treated as a metaphorical spell with a prototype delivery profile. Canonical reference input: Mordenkainen’s Sword (spell).
When To Use
- You need a long-running background process, scheduled task, or watcher with a single clear mandate.
- A recurring precise action should persist without manual babysitting once it is safely launched.
- The right abstraction is a narrow autonomous worker, not a broad orchestration system.
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 worker's single mandate, cadence, start conditions, and stop conditions.
- Design the loop for idempotence, observability, safe retries, and deliberate dismissal.
- Return a runnable spec with lifecycle hooks, failure handling, and operator controls.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A daemon, cron, or persistent worker design for the task.
- Lifecycle and cancellation rules for starting, monitoring, and stopping it safely.
- Monitoring, error-recovery, and escalation notes for ongoing operation.
Pitfalls / Guardrails
- Call out the glue, permissions, or missing infrastructure before you imply this is fully operational.
- Do not give the process broader authority than the single job requires.
- Ensure repeated actions are idempotent or explicitly bounded so persistence does not accumulate damage.
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 · 67 lines · 66 tokens per session scan A 59d88452d7bb
mordenkainen-s-sword 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 66 tokens to every session and 673 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.