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.
Verification
- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check that the metaphor still maps cleanly to a real operational mechanism.
- Check that any missing glue code, permissions, or future work is labeled before the skill is treated as ready.
Example Invocation
/mordenkainen-s-sword design a persistent worker for this single job, including how it starts, reports, and stops
1---2name: mordenkainen-s-sword-23description: 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.4license: CC0-1.05---6# Mordenkainen’s Sword7Summon a standing process that keeps cutting through one job until dismissed.8## What This Skill Does9Use 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.10In this grimoire, Mordenkainen’s Sword is treated as a metaphorical spell with a prototype delivery profile.11Canonical reference input: Mordenkainen’s Sword (spell).12## When To Use1314- You need a long-running background process, scheduled task, or watcher with a single clear mandate.15- A recurring precise action should persist without manual babysitting once it is safely launched.16- The right abstraction is a narrow autonomous worker, not a broad orchestration system.1718## Prerequisites1920- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.2122## Procedure23241. Restate the target, the success condition, and any no-touch boundaries before taking action.252. Define the worker's single mandate, cadence, start conditions, and stop conditions.263. Design the loop for idempotence, observability, safe retries, and deliberate dismissal.274. Return a runnable spec with lifecycle hooks, failure handling, and operator controls.285. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.2930## Deliverables3132- A daemon, cron, or persistent worker design for the task.33- Lifecycle and cancellation rules for starting, monitoring, and stopping it safely.34- Monitoring, error-recovery, and escalation notes for ongoing operation.3536## Pitfalls / Guardrails3738- Call out the glue, permissions, or missing infrastructure before you imply this is fully operational.39- Do not give the process broader authority than the single job requires.40- Ensure repeated actions are idempotent or explicitly bounded so persistence does not accumulate damage.4142## Verification4344- Check that the result includes every deliverable promised above.45- Check that confirmed facts, assumptions, and inferences are visibly separated.46- Check that the metaphor still maps cleanly to a real operational mechanism.47- Check that any missing glue code, permissions, or future work is labeled before the skill is treated as ready.4849## Example Invocation50```text51/mordenkainen-s-sword design a persistent worker for this single job, including how it starts, reports, and stops52```
Hmbown