What to look for
- Clear display name, description, kind, and tags.
- Approved package assets with pet.json and a valid spritesheet.
- Stable page URL, package URL, and install command.
- Share snippets for README badges, animated cards, and embeds.
- MCP and OpenAPI resources that agents can inspect directly.
Best fit by workflow
- For quick setup, choose pets with a clear slug, concise description, and a ready
npx @astandrik/codex-pets install <slug>command. - For agent recommendations, prefer pets with descriptive tags such as pixel, cute, fantasy, terminal, minimal, anime, or space.
- For documentation and READMEs, choose pets with badge, card, and iframe snippets exposed by the share route or MCP tools.
- For pack validation, confirm the package contains pet.json plus a spritesheet.webp or spritesheet.png atlas at the expected Codex size.
Agent-friendly setup
codex mcp add codexPets --url https://pets.ydb-qdrant.tech/mcp
npx @astandrik/codex-pets install <slug>