Petdex is a gallery, installer, and desktop application for animated pets that accompany coding agents. People browse and submit pets through its website, install them with a command-line tool, and use the desktop app to display reactions to agent activity. The catalogue includes skills and instructions for creating or using these pets with supported coding agents.
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 agentmods add instructions/crafter-station/petdex/agents-mdgit clone --depth 1 https://github.com/crafter-station/petdexWrote 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/instructions/crafter-station/petdex/agents-md)<a href="https://agentmods.dev/instructions/crafter-station/petdex/agents-md"><img src="https://agentmods.dev/badge/instructions/crafter-station/petdex/agents-md.svg" alt="Measured on agentmods" 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.01180 | $0.01180 |
| Opus 5 | $0.00590 | $0.00590 |
| Sonnet 5 | $0.00236 | $0.00236 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
petdex AGENTS.md 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 6d 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Petdex Agent Notes
Commands
- Use Bun for repo work:
bun install, notnpm install. Published CLI docs mentionnpm/npxfor end users only. - Recommended local app dev is
bun run dev:docker; it boots local Postgres and Redis with shared Clerk dev defaults from.env.dev. - Maintainer dev is
bun devwith.env.localcopied from.env.example; this path expects Clerk, Postgres/Neon, R2, Upstash, Resend, OpenAI, and ElevenLabs credentials. bun run dev:mockis deprecated and intentionally exits. Keep.env.mockonly for targeted mock-backed tests or build checks.- Root checks:
bun run checkfor Biome,bun run formatto write Biome fixes,bun run buildfor the Next app,bun testfor Bun tests, andbun run i18n:checkafter editing translation messages. There is no roottypecheckscript. - Focused tests use
bun test path/to/file.test.ts. Tests that importsrc/lib/db/client.tsdirectly or indirectly, includingsrc/lib/pet-search.test.tsandsrc/lib/security.test.ts, need a usableDATABASE_URLor mock env:bun test --env-file=.env.mock src/lib/security.test.ts. packages/petdex-cliandpackages/discord-botare independent packages, not root workspaces; run their ownbun installand package scripts from inside each directory. Roottsconfig.jsonexcludespackages.- CLI package verification, run from
packages/petdex-cli, isbun run build && bun run typecheck; the build emits ignoreddist/petdex.jsand prepends the node shebang inpostbuild. - Discord bot work stays in
packages/discord-bot; usebun run register,bun run dev, orbun run startthere with env frompackages/discord-bot/.env.example.
Architecture
- Main app routes live in
src/app/[locale]; API routes live insrc/app/api; shared server/domain code lives insrc/lib; DB schema issrc/lib/db/schema.tswith SQL migrations indrizzle/. - This is Next
16.2.4with newer conventions:src/proxy.tsis the middleware/proxy entrypoint, route/layoutparamsare promises, andsrc/app/layout.tsxintentionally returns children while[locale]/layout.tsxowns<html>/<body>for localelang. If touching framework APIs, prefer the installed Next docs undernode_modules/next/dist/docs/over older assumptions. - i18n locales are
en,es, andzh; message files are undersrc/i18n/messages/, andnext-intlis wired throughsrc/i18n/request.tsplus the locale layout. - Mock DB bootstrap tolerates migration/schema drift via fixups in
src/lib/mock/db.ts; if schema fields are added and mock pages fail, update those fixups until a real migration lands. drizzle.config.tshard-fails withoutDATABASE_URL; there are no root package scripts for migration generation or application, and manyscripts/apply-*/backfill-*files are real-DB one-offs.- Automated review/tag/sound paths use AI SDK model strings through Vercel AI Gateway (
AI_GATEWAY_API_KEYin.env.example); avoid adding raw OpenAI client wiring to server paths.
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.
- 6d ago First seen · 30 lines · 1,180 tokens per session scan A 193414bcc5da
petdex AGENTS.md is an instructions file published in the GitHub repository crafter-station/petdex (4,039 stars, last pushed 5d ago), licensed MIT. It adds 1,180 tokens to every session, about $0.0059 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-08-30.
Other instructions, from other repositories
supermemory CLAUDE.md
Claude Code instructions for supermemoryai/supermemory, covering claude.md, repository structure, applications (apps/), development commands and root level (monorepo).
create-better-t-stack AGENTS.md
AGENTS.md instructions for AmanVarshney01/create-better-t-stack, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and error handling conventions.
Better-Fullstack AGENTS.md
AGENTS.md instructions for Marve10s/Better-Fullstack, covering guidelines, web ui, workflow and bun.
better-drizzle AGENTS.md
AGENTS.md instructions for almeidazs/better-drizzle, covering better-drizzle repository – agent field notes, architecture, design intent, api surface and performance rules.
kan AGENTS.md
AGENTS.md instructions for kanbn/kan, covering agents.md, project overview, setup commands, project structure and code style.
flarestarter AGENTS.md
Instructions for FlareStarter/flarestarter, covering agents.md, what this is, structure, conventions and commands.