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 locate-animals-or-plantsgit 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/locate-animals-or-plants)<a href="https://agentmods.dev/skills/hmbown/wizards-of-the-ghosts/locate-animals-or-plants"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/locate-animals-or-plants/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/locate-animals-or-plants"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/locate-animals-or-plants.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.00072 | $0.00646 |
| Opus 5 | $0.00036 | $0.00323 |
| Sonnet 5 | $0.00014 | $0.00129 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade A, and why
locate-animals-or-plants 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.
Locate Animals or Plants
Find what is alive, where it lives, and what it is feeding on.
What This Skill Does
Locate Animals or Plants is service discovery with ecological instincts. It helps you find running services, background jobs, data stores, dependency roots, and other living things in an environment before you touch them. The point is not just location, but context: what is active, who depends on it, and what keeps it alive. In this grimoire, Locate Animals or Plants is treated as a metaphorical spell with a shipping-now delivery profile. Canonical reference input: Locate Animals or Plants (spell).
When To Use
- You need an inventory of active services, dependencies, or data flows in an unfamiliar environment.
- The problem involves discovering what is running rather than debugging one known component.
- You suspect there are hidden dependencies or stale registrations mixed in with live systems.
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.
- Sweep the environment for active services, scheduled jobs, stores, queues, and known dependency markers.
- Trace the discovered components to the systems they depend on or feed.
- Return a live-system map with confidence levels and any blind spots in the survey.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A discovery map of live services and dependencies.
- A shortlist of the most likely roots, leaves, and chokepoints.
- A confidence note on stale entries, missing telemetry, or unobservable zones.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Do not mistake stale config, dead DNS, or abandoned containers for living systems without corroborating signals.
- Stay within authorized discovery boundaries when scanning networks or environments.
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 · 72 tokens per session scan A 78df261f58f1
locate-animals-or-plants 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 72 tokens to every session and 646 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
n8n-workflows
Use when n8n workflow automation — nodes, triggers, expressions, credentials, webhooks, error handling. Use when working with n8n workflows.
pipedream-workflows
Use when pipedream serverless workflows — triggers, code steps, pre-built actions, data stores, HTTP. Use when working with pipedream workflows.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
devex-sdk-design
Developer experience (DX) engineering, SDK design patterns, API ergonomics, CLI tooling design, documentation-driven development, and developer onboarding. Use when designing SDKs, improving API ergonomics, building developer tools, or creating developer documentation.
api-design
REST API contract designer and reviewer. ALWAYS use when designing new endpoints, reviewing existing API contracts, planning API versioning, or standardizing error models. Covers resource modeling (URL/naming), HTTP method semantics, status code selection, error model consistency, pagination/filtering/sorting…
kafka-event-driven-design
Kafka event-driven architecture designer and reviewer, at the application/client layer. ALWAYS use when designing, reviewing, or troubleshooting how a service produces or consumes Kafka events — topic and partition-key design, producer and consumer client configuration, consumer group topology, event schema definition…