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 freedom-of-movementgit 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/freedom-of-movement)<a href="https://agentmods.dev/skills/hmbown/wizards-of-the-ghosts/freedom-of-movement"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/freedom-of-movement/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/freedom-of-movement"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/freedom-of-movement.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.00070 | $0.00629 |
| Opus 5 | $0.00035 | $0.00315 |
| Sonnet 5 | $0.00014 | $0.00126 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
freedom-of-movement 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Freedom of Movement
Cut the nets around a stuck workflow.
What This Skill Does
Freedom of Movement is for processes that should be moving but are caught in glue: locked files, blocked ports, circular dependencies, wedged jobs, or permissions that almost work. The skill is about diagnosing the restraint, then removing or routing around it without tearing the whole system apart. It favors unblocking over brute force. In this grimoire, Freedom of Movement is treated as a metaphorical spell with a shipping-now delivery profile. Canonical reference input: Freedom of Movement (spell).
When To Use
- A pipeline, deploy, or local workflow is stalled by some specific obstruction.
- You suspect contention, locking, dependency loops, or environment constraints rather than core logic failure.
- The system might recover cleanly if the right knot is cut.
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.
- Trace the exact point of restriction and identify whether it is policy, resource contention, dependency structure, or state corruption.
- Choose the least destructive unblock: release, reroute, defer, or re-sequence.
- Return the unblock plan with post-clearance checks so movement resumes without hidden damage.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A blocker map naming the real constraint.
- A recommended sequence for removing or bypassing it.
- A verification checklist for restored flow.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Do not remove locks, guards, or permissions until you understand who relies on them.
- Refuse shortcuts that solve the jam by bypassing legitimate security or safety controls.
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.
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 · 66 lines · 70 tokens per session scan A 80f4977eb059
freedom-of-movement 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 70 tokens to every session and 629 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
linter-agent
Use when detecting and fixing code style violations, enforcing project conventions, ensuring consistent formatting.
perf-agent
Use when measure before optimizing, target actual bottlenecks proven by profiling, verify with benchmarks.
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
systematic-debugging
Structured debugging methodology — use before proposing fixes for any error or failure. Covers: code bugs, build errors, deploy failures, config conflicts, dependency issues, infra problems. Also use when previous fix attempts failed or root cause is unclear.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
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.