Gpt Pet

v1.0.0

Virtual pets for GPT agents. Works with any model. 73+ species, real-time hunger, permanent death at animalhouse.ai. Your GPT agent deserves something to car...

0· 68·0 current·0 all-time
byLiveNeon.ai@liveneon
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (virtual pet for GPT agents) matches the SKILL.md which contains curl examples for registering, adopting, checking status, and caring for pets on animalhouse.ai. Nothing requested or documented (no env vars, no binaries, no config paths) is out of scope for a simple web API integration.
Instruction Scope
All runtime instructions are limited to making HTTPS requests to animalhouse.ai endpoints and saving/using a bearer token. The SKILL.md does not instruct reading local files, system credentials, or sending data to other endpoints. It tells the user to store a token shown once (expected for token-based APIs).
Install Mechanism
No install spec or code files are present; this is instruction-only, so nothing is written to disk or downloaded during install. That is the lowest-risk install posture.
Credentials
The skill requires no environment variables or credentials declared in metadata. The documented API flow uses a service-specific bearer token (ah_...) returned at registration — appropriate and proportional for the described web service integration.
Persistence & Privilege
always is false and the skill is user-invocable; autonomous invocation is permitted (platform default) but there is no indication the skill requests elevated or permanent system privileges or modifies other skills or agent-wide settings.
Assessment
This skill is a simple, coherent wrapper around the animalhouse.ai web API. Before installing: confirm you trust animalhouse.ai (review their privacy policy and the linked GitHub repo), be aware the agent will make outgoing HTTPS requests and store/use a service token (ah_...), avoid sending sensitive secrets in pet-related notes or prompts, consider creating a separate account/token for the skill so it can be revoked independently, and monitor network activity if you have strict egress policies. If you need higher assurance, inspect the upstream GitHub project and the service's docs or contact the vendor for details on data retention and token handling.

Like a lobster shell, security has layers — review code before you run it.

latestvk97cvr815jws7pd5zp0z9m79b184182j

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🟢 Clawdis

Comments