Borrowing it
Nothing to install: this file belongs to portons/codex-pet-share. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/portons/codex-pet-share/master/.agents/skills/petshare-setup/SKILL.mdgit clone --depth 1 https://github.com/portons/codex-pet-shareWrote 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/portons/codex-pet-share/petshare-setup)<a href="https://agentmods.dev/skills/portons/codex-pet-share/petshare-setup"><img src="https://agentmods.dev/badge/skills/portons/codex-pet-share/petshare-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/portons/codex-pet-share/petshare-setup"><img src="https://agentmods.dev/badge/skills/portons/codex-pet-share/petshare-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 97 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 115 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00048 | $0.01774 |
| Opus 5.5 | $0.00019 | $0.00710 |
| Sonnet 5.5 | $0.00010 | $0.00355 |
| Haiku 4.5 | $0.00005 | $0.00177 |
Grade A, and why
petshare-setup 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 2mo 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Petshare Setup
Use this skill when an agent is asked to spin up, fork, rebrand, deploy, or modify this repository or a close derivative. The app is a self-hostable React/Vite pixel-pet sharing surface: users upload Codex-compatible pet packages, browse animated previews, download packages/GIFs, and join multiplayer playground rooms.
This is a repo-scoped Codex skill. Keep it under
.agents/skills/petshare-setup/ so Codex can discover it from the repository.
First Read
Before editing, read:
README.mddocs/GETTING_STARTED.mddocs/PROVIDER_ADAPTERS.mdAGENTS.mdreferences/petshare-architecture.mdwhen touching app behavior, uploads, previews, animations, rooms, provider adapters, or deploymentreferences/security-boundary.mdwhen publishing, documenting public setup, reviewing exposure risk, or changing auth/moderation/provider surfaces
Non-Negotiables
- Keep changes literal to the request. Do not add fallbacks, backwards compatibility, provider-specific public env vars, or unrelated hardening.
- Keep the browser public contract provider-neutral. Public build vars are only:
VITE_APP_API_BASE_URL,VITE_PUBLIC_APP_ORIGIN,VITE_REALTIME_URL,VITE_REALTIME_PUBLIC_KEY,VITE_APP_NAME,VITE_APP_HANDLE,VITE_APP_TAGLINE, andVITE_APP_REPO_URL. - Never commit
.env,.env.local, API tokens, salts, database passwords, provider account identifiers, generated migration exports, or local auth data. - Use provider adapters as replaceable boundaries. Feature code under
src/should not branch on provider names. - Do not turn this skill into an abuse manual. Do not add copy-paste scripts, unauthenticated client examples, raw room-event payload recipes, rate-limit thresholds, bypass instructions, scraping loops, or moderation-evasion advice.
- For ports, follow
AGENTS.md: check a requested port before starting a process, and never kill reserved ports unless explicitly asked.
Core Workflow
- Identify whether the task is setup, provider work, upload/asset work, preview/GIF work, animation/playground work, multiplayer rooms, rebranding, or security/publication review.
- Load only the reference file needed for that surface.
- Inspect current source before deciding; this repo has explicit adapter and feature boundaries.
- Make the smallest code/doc changes that satisfy the user request.
- Run the relevant validation commands below.
- If publishing or handing off public code, run the exposure checks from
references/security-boundary.md.
What ships with it
3 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.
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.
- 2mo ago First seen · 183 lines · 48 tokens per session scan A c601a27b71a2
petshare-setup is a skill published in the GitHub repository portons/codex-pet-share (142 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,774 once invoked, about $0.0002 per session on Opus 5.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.
petshare-setup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| petshare-setupportons/codex-pet-share | Skill | 142 | 1mo ago | MIT | A | 48 | Codex |
| playtest-reportDonchitos/Claude-Code-Game-Studios | Skill | 37k | 20d ago | MIT | A | 20 | Claude Code |
| godot-signals-groupsgamedev-skills/awesome-gamedev-agent-skills | Skill | 7.4k | 11d ago | Apache-2.0 | A | 95 | Claude Code |
| texture-workflowarjun988/blender-skills | Skill | 2.0k | 2d ago | MIT | A | 41 | Claude Code |
| scenario-unreal-gameplayscenario-labs/skills | Skill | 3.5k | yesterday | MIT | A | 121 | Claude Code |
| motionOpenDCAI/GameFactory-3A | Skill | 1.0k | 10d ago | Apache-2.0 | A | 0 | Claude Code, Codex |
| unity-addressablesBesty0728/Unity-Skills | Skill | 1.9k | today | MIT | A | 25 | Claude Code, Codex |