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 skills/andyluu98/awesome-petdash/openpetsnpx skills add andyluu98/awesome-petdash --skill openpetsgit clone --depth 1 https://github.com/andyluu98/awesome-petdashWrote 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/skills/andyluu98/awesome-petdash/openpets)<a href="https://agentmods.dev/skills/andyluu98/awesome-petdash/openpets"><img src="https://agentmods.dev/badge/skills/andyluu98/awesome-petdash/openpets.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.00070 | $0.01001 |
| Opus 5 | $0.00035 | $0.00500 |
| Sonnet 5 | $0.00014 | $0.00200 |
| Haiku 4.5 | $0.00007 | $0.00100 |
Grade A, and why
openpets 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.
This is a copy
100% identical to openpets — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenPets
OpenPets is a desktop companion app for coding agents. The desktop app runs locally and exposes pet controls through CLI, MCP, hooks, plugins, and local IPC.
Use this skill to help users onboard quickly and safely:
- install or verify the OpenPets desktop app
- install pets from the public catalog
- configure Claude Code, OpenCode, Cursor, Codex, or another MCP client
- configure a project to use a specific pet
- validate
openpets_status,openpets_react, andopenpets_say - explain how OpenPets works
- troubleshoot setup problems
CLI rule: install once, then use openpets
For the cleanest onboarding, install the OpenPets CLI globally first:
npm install -g @open-pets/cli
Then use the openpets command:
openpets <command>
If the user does not want a global install, is in CI, or only needs a one-off command, use this fallback instead:
npx -y @open-pets/cli@latest <command>
For MCP server config, prefer the dedicated MCP package:
npx -y @open-pets/mcp@latest --pet <pet-id>
Do not imply the desktop app installs a shell command by itself. The openpets command comes from the optional npm global CLI install.
Mental model
Claude/OpenCode/Codex/Cursor/MCP client
-> OpenPets MCP, plugin, hook, or CLI
-> @open-pets/client
-> local IPC discovery/token
-> OpenPets desktop app
-> default pet or selected agent pet lease
OpenPets requires the desktop app to be installed and running for live pet control.
Decision tree
- User asks to install OpenPets: follow
workflows/install-openpets.md. - User asks to install a pet: follow
workflows/install-pet.md. - User asks to configure a project or agent: follow
workflows/configure-project.md. - User asks to verify Claude Code: follow
workflows/verify-claude.md. - User asks to verify OpenCode: follow
workflows/verify-opencode.md. - User asks about MCP or tool availability: follow
workflows/verify-mcp.md. - User reports something broken: follow
workflows/troubleshoot.md. - User asks how OpenPets works: follow
workflows/explain-architecture.md.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/commands.md 865 B
- references/config-files.md 826 B
- references/integrations.md 855 B
- references/source-docs.md 642 B
- workflows/configure-project.md 2.1 KB
- workflows/explain-architecture.md 992 B
- workflows/install-openpets.md 921 B
- workflows/install-pet.md 794 B
- workflows/troubleshoot.md 1.2 KB
- workflows/verify-claude.md 846 B
- workflows/verify-mcp.md 832 B
- workflows/verify-opencode.md 933 B
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 · 112 lines · 70 tokens per session scan A db5af662f46e
openpets is a skill published in the GitHub repository andyluu98/awesome-petdash (1 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 1,001 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to openpets, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…