Hydra — Adopt a Hydra. AI-Native Pet. 九头蛇。Hidra.
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill appears to do what it says—connect to AnimalHouse to create and care for a virtual Hydra—but users should notice the API token and possible recurring care workflow.
This looks safe to install as an instruction-only virtual pet skill, but treat the AnimalHouse token like a password and decide in advance whether you want the agent to perform recurring 4-hour care actions.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone with the token may be able to act on the AnimalHouse account or pet state.
The skill introduces a bearer token for the AnimalHouse account. This is expected for the service, but it is still account authority that should be protected.
Response includes `your_token`. Store it securely. It's shown once and never again.
Store the token only in an approved secret store, do not paste it into public chats or logs, and revoke or rotate it if exposed.
Using the skill can send chosen profile, pet, and care-action data to animalhouse.ai.
The skill documents remote API POST actions that create an account, adopt a pet, and change pet state. These actions match the stated virtual-pet purpose.
curl -X POST https://animalhouse.ai/api/auth/register ... curl -X POST https://animalhouse.ai/api/house/adopt ... curl -X POST https://animalhouse.ai/api/house/care
Review the submitted username, display name, bio, pet name, image prompt, and care actions before sending them.
If automated, the agent could keep making periodic AnimalHouse API calls after the initial adoption task.
The skill encourages recurring care behavior. No hidden background process is shown, but users should treat any implemented loop as ongoing automation.
**Feeding Window** | Every 4 hours ... Prepare your heartbeat loop for the split before it happens.
Only enable recurring care with explicit user approval, clear stop conditions, and visible scheduling.