search-codex-pets

openpets.sh/search-codex-pets-f0oals · updated May 21, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$browse install openpets.sh/search-codex-pets-f0oals
0 commentsdiscussion
summary

Search the OpenPets community registry for Codex / Claude Code / OpenCode / Pi Code pets matching user criteria, returning ranked pet metadata and universal one-click install links for the OpenPets macOS app.

skill.md
name
search-codex-pets
title
Search OpenPets Codex Pet Registry
description
>- Search the OpenPets community registry for Codex / Claude Code / OpenCode / Pi Code pets matching user criteria, returning ranked pet metadata and universal one-click install links for the OpenPets macOS app.
website
openpets.sh
category
developer-tools
tags
- codex - openpets - registry - search - ai-tools - macos
source
'browserbase: agent-runtime 2026-05-19'
updated
'2026-05-19'
recommended_method
api
alternative_methods
- method: browser rationale: >- Drive the public gallery UI (form#gallery-form on openpets.sh) as a fallback if /api/pets becomes unreachable. Strictly slower due to IntersectionObserver-driven lazy loading; the JSON API returns the same records in one round trip.
verified
true
proxies
true

Search OpenPets Codex Pet Registry

Purpose

Anonymously search the OpenPets community registry — the largest catalog of pixel-art "pets" (desktop companions) built for Codex, Claude Code, OpenCode, and Pi Code — and return ranked pet metadata plus a universal one-click install link suitable for handoff to the OpenPets macOS app. Read-only. No authentication required. Returns JSON.

When to Use

  • A user wants pets matching free-text criteria ("show me cat pets", "find a dragon", "anime girl with a staff").
  • A user wants to filter by pet kind: animal, creature, object, or person.
  • A user wants the most-popular, most-liked, or newest pets in the registry.
  • A user wants a copy-pasteable install link to hand to the OpenPets macOS app (or share with a friend who has it installed).
  • A user wants the preview spritesheet / share image URL for a pet to embed in a chat or doc.

Workflow

The OpenPets website exposes a public, paginated REST endpoint at /api/pets that powers the on-page gallery. Always prefer this over scripted browsing — no auth, no rate limits observed, returns the full record set including install-link material in one round trip.

  1. Issue a single GET to the search endpoint:

    GET https://openpets.sh/api/pets?q={query}&kind={kind}&sort={sort}&page={n}&pageSize={n}
    Accept: application/json
    
  2. Map user criteria to query params:

    ParamTypeRequiredNotes
    qstringnoFull-text search over displayName, description, and tags. URL-encode it.
    kindenumnoOne of animal, creature, object, person. Any other value returns zero results (total: 0).
    sortenumnoOne of new (default), popular, liked. Invalid values silently fall back to new.
    pageintno1-indexed. Default 1.
    pageSizeintnoDefault ~24. pageSize=100 works; upper bound undocumented.
  3. Parse the JSON response. Top-level shape:

    { "page": 1, "pageSize": 24, "total": 239, "totalPages": 10,
      "generatedAt": "2026-05-18T11:13:49.412Z", "pets": [ ... ] }
    
  4. For each pet in pets[], extract:

    • id — slug used in URLs (e.g. qwq, apupepe, aobing)
    • displayName, description, kind, ownerName, tags[]
    • viewCount, downloadCount, likeCount
    • previewUrl (relative /api/pets/{id}/preview) — animated WebP preview
    • spritesheetUrl (relative /api/pets/{id}/spritesheet) — full sprite atlas
    • shareImageUrl — 1200×630 OpenGraph card
  5. Construct the install link for each pet:

    https://openpets.sh/install/{pet.id}
    

    This URL is public and anonymous. Hitting it returns a 302 with:

    Location: openpets://install?url=<signed-download-url-with-ticket>&id={pet.id}
    

    The signed ticket is a server-issued JWT-style token with a ~24h expiry (exp, nonce, id payload). The OpenPets macOS app intercepts the openpets:// protocol and pulls the bundle. Always hand out the https://openpets.sh/install/{id} URL — never try to construct the openpets:// deep-link yourself (the ticket is server-signed).

  6. Optional detail enrichment: GET https://openpets.sh/api/pets/{id} returns { "pet": { ... } } with the same record shape if you need a single record without searching.

  7. Return the ranked list with id, displayName, description, kind, ownerName, tags, stats, previewUrl, and installUrl.

Browser fallback

If /api/pets ever becomes unreachable, drive the gallery UI directly. This is strictly slower (lazy-loaded sprites, IntersectionObserver pagination) but the contract is stable:

  1. Open https://openpets.sh. Optionally pre-seed query state via URL params (?q=cat&kind=animal&sort=popular) — the gallery script reads them on load.
  2. Fill input#q with the search term, set select#sort and select#kind.
  3. Click button[type="submit"] inside form#gallery-form.
  4. Wait for #gallery-results to populate. Each card is <article class="pet-card"> with a link <a class="pet-card-preview-link" href="/pets/{id}">.
  5. Read pet IDs from the href attribute. Construct install URLs as https://openpets.sh/install/{id}.
  6. To paginate, scroll #gallery-sentinel into view or click #load-more-pets.

No proxies or stealth required for either path — the site is behind Cloudflare but the API and gallery are CORS-open and bot-tolerant.

Site-Specific Gotchas

  • Two response shapes from /api/pets depending on sort order. With sort=new (the default), the response is served from a registry mirror and includes lighter, mirror-flavored fields: installTicketUrl, downloadUrl, validationReport, source.apiBase, mirroredAt, registryNumber. With sort=popular or sort=liked, the response is served live from the primary database and includes richer fields: spritesheetPath, ownerId, ownerHandle, likedByMe, reactionCounts, myReactions, ownerShadowbanned. Both share the core set (id, displayName, description, kind, ownerName, tags, uploadedAt, viewCount, downloadCount, likeCount). Don't depend on the extended fields being present.

  • Invalid kind ⇒ empty results; invalid sort ⇒ silent fallback. kind=foo returns total: 0; sort=foo returns the full registry sorted by new. Validate kind against the enum before sending or you'll mislead the user with "0 matches".

  • installTicketUrl and downloadUrl in the response require auth. POST /api/pets/{id}/install-ticket returns 404 anonymously, and GET /api/pets/{id}/download returns 401 {"error":"download ticket required"}. Ignore those fields for anonymous flows. The public /install/{id} redirect is the supported anonymous path; it generates the signed ticket server-side and embeds it in the openpets:// Location header.

  • /install/{id} requires the OpenPets macOS app to actually resolve. The openpets:// URI scheme is registered by the app from the alterhq/openpets release. Users on Linux/Windows, or macOS without the app, will see "no app to handle this URL". If unsure, prefix the response with a one-liner: "Install OpenPets first, then click the install links."

  • Registry has two upstream sources. Pets mirrored from codex-pets.net (the original Codex Pet Share, which OpenPets succeeded) carry a source.apiBase field and mirroredAt timestamp; native OpenPets uploads don't. Useful for de-duping if a user uploads to both registries.

  • Catalog size: ~3,500 pets as of May 2026. Default pageSize=24; pageSize=100 is fine. Don't paginate past totalPages — the gallery JS loops back to page 1 in that case, which would loop your scraper.

  • Read-only via the API. Liking, favoriting, uploading, commenting all require a Cloudflare Access + Supabase session. Don't promise mutation flows from an anonymous client. For uploads point users to /upload in the OpenPets web app after signin.

  • Pet IDs are author-chosen slugs (qwq, aobing, apupepe, ro-job-female-runeknightdragon) — not UUIDs. They're URL-safe but can be long. Don't try to alphabetize them — they aren't ordered.

  • No anti-bot wall observed. Cloudflare is configured permissively for the registry: anonymous GET /api/pets, anonymous GET /api/pets/{id}, and anonymous GET /install/{id} all return 200/302 without challenges from datacenter IPs. Browser fallback also works without --verified / --proxies flags, though the metadata in this skill was captured with both enabled as a defensive default.

Expected Output

Recommended return shape per query (one of three outcomes):

A — Successful search (q="cat"):

{
  "query": { "q": "cat", "kind": null, "sort": "new", "page": 1, "pageSize": 24 },
  "total": 239,
  "totalPages": 10,
  "pets": [
    {
      "id": "qwq",
      "displayName": "qwq",
      "description": "Neutral cool white-haired cat-tail pet: aloof outside, warm inside, cute, playful, and subtly enchanting.",
      "kind": "person",
      "ownerName": "taytaya",
      "tags": [],
      "uploadedAt": "2026-05-17T15:06:19.058Z",
      "stats": { "views": 14, "downloads": 0, "likes": 0 },
      "previewUrl": "https://openpets.sh/api/pets/qwq/preview",
      "spritesheetUrl": "https://openpets.sh/api/pets/qwq/spritesheet",
      "shareImageUrl": "https://openpets.sh/api/pets/qwq/share.png",
      "detailUrl": "https://openpets.sh/pets/qwq",
      "installUrl": "https://openpets.sh/install/qwq"
    }
  ]
}

B — Kind-filtered popular search (kind="animal", sort="popular"):

{
  "query": { "q": null, "kind": "animal", "sort": "popular", "page": 1, "pageSize": 2 },
  "total": 2072,
  "totalPages": 1036,
  "pets": [
    {
      "id": "apupepe",
      "displayName": "Pepe",
      "description": "A compact Codex-style green frog pet in a plain blue shirt.",
      "kind": "animal",
      "ownerName": "kegashin",
      "tags": ["cute", "animated", "pixel", "animal", "celeb", "mascot"],
      "stats": { "views": 601, "downloads": 0, "likes": 5 },
      "previewUrl": "https://openpets.sh/api/pets/apupepe/preview",
      "spritesheetUrl": "https://openpets.sh/api/pets/apupepe/spritesheet",
      "detailUrl": "https://openpets.sh/pets/apupepe",
      "installUrl": "https://openpets.sh/install/apupepe"
    }
  ]
}

C — Empty results (no matches):

{
  "query": { "q": "unicornthatdoesnotexist", "kind": null, "sort": "new", "page": 1, "pageSize": 24 },
  "total": 0,
  "totalPages": 0,
  "pets": []
}

For outcome C, surface to the user: "No OpenPets match your criteria. Try a broader term, drop the kind filter, or browse the newest pets at https://openpets.sh."

how to use search-codex-pets

How to use search-codex-pets on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add search-codex-pets
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$browse install openpets.sh/search-codex-pets-f0oals

The skills CLI fetches search-codex-pets from GitHub repository openpets.sh/search-codex-pets-f0oals and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/search-codex-pets

Reload or restart Cursor to activate search-codex-pets. Access the skill through slash commands (e.g., /search-codex-pets) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.549 reviews
  • Ganesh Mohane· Dec 20, 2024

    Solid pick for teams standardizing on skills: search-codex-pets is focused, and the summary matches what you get after install.

  • Aditi Singh· Dec 16, 2024

    search-codex-pets fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Shikha Mishra· Dec 12, 2024

    search-codex-pets reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Aanya Wang· Nov 19, 2024

    Solid pick for teams standardizing on skills: search-codex-pets is focused, and the summary matches what you get after install.

  • Michael Chen· Nov 7, 2024

    search-codex-pets is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Yash Thakker· Nov 3, 2024

    I recommend search-codex-pets for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Kiara Mensah· Oct 26, 2024

    Keeps context tight: search-codex-pets is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Dhruvi Jain· Oct 22, 2024

    Useful defaults in search-codex-pets — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Fatima Robinson· Oct 10, 2024

    search-codex-pets has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Sofia Iyer· Oct 10, 2024

    Solid pick for teams standardizing on skills: search-codex-pets is focused, and the summary matches what you get after install.

showing 1-10 of 49

1 / 5