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 prestidigitationgit 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/prestidigitation)<a href="https://agentmods.dev/skills/hmbown/wizards-of-the-ghosts/prestidigitation"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/prestidigitation/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/prestidigitation"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/prestidigitation.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.00075 | $0.01027 |
| Opus 5 | $0.00037 | $0.00513 |
| Sonnet 5 | $0.00015 | $0.00205 |
| Haiku 4.5 | $0.00007 | $0.00103 |
Grade A, and why
prestidigitation 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prestidigitation
Handle quick, low-stakes utility tasks that do not deserve a full spell.
What This Skill Does
Prestidigitation transforms. It does not fix, build, scaffold, migrate, or actuate. If the user says "make this look better" or "convert this to that format" — use prestidigitation. If the user says "make this work" or "set this up" or "build this system" — use something else. In this grimoire, Prestidigitation is treated as a hybrid spell with a shipping-now delivery profile. Canonical reference input: Prestidigitation (spell).
When To Use
- Trigger this spell when the request contains:
- Format/transform verbs: reformat, convert, sort, strip, encode, decode, tidy, clean, pretty-print
- Scale qualifiers: quick, just, small, one-off, throwaway, simple, nothing fancy, straightforward
- Artifact types: a table, a list, a single file, a string, a UUID, a snippet, a blob
- Bounded counts: "about 20", "10 rows", "5 columns", "one line", "a few"
- The task is cantrip-scale when all three are true:
- The input fits in a single message or small file
- The output is a single artifact (text, table, string, file)
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.
- Scope check: Confirm the task is single-input → single-output. If it spans multiple files or needs external services, stop and recommend the correct spell.
- Execute directly: Perform the transformation in-session. Do not create scaffolding, config files, or helper scripts. Do the work, do not build the tool to do the work.
- Return result: Output the artifact immediately. Add one sentence explaining what was done.
- Escalate if needed: If mid-execution the task reveals hidden complexity (nested edge cases, data too large, ambiguous requirements), stop and name the appropriate full spell.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
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 · 73 lines · 75 tokens per session scan A a10fc09c9443
prestidigitation 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 75 tokens to every session and 1,027 once invoked, about $0.0004 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.