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/young1the/pets-driven/agents-mdgit clone --depth 1 https://github.com/young1the/pets-drivenWhat 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 | $0.01500 | $0.01500 |
| Opus 5 | $0.00750 | $0.00750 |
| Sonnet 5 | $0.00300 | $0.00300 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade A, and why
pets-driven 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 yesterday.
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Pets-Driven is a Windows desktop app (Tauri + React) where a pet represents one bound coding-agent execution, plus the landing site and shared packages around it. Start with CONTEXT.md for the domain language and ARCHITECTURE.md for how the modules connect.
Language
- All code comments, JSDoc, and in-repo documentation (Markdown, ADRs, READMEs) must be written in English.
- Git commit messages and pull request descriptions must also be written in English.
- This applies to source files, type definitions, test descriptions, and any docs committed to the repository.
- Conversations and chat with the user may continue in Korean; only artifacts written to disk or git history are English-only.
Commands
pnpm dev # desktop app (Tauri)
pnpm dev:playground # simulation playground in the browser
pnpm dev:design # design-system component gallery
pnpm test # every package's suite + scripts/*.test.mjs
pnpm typecheck # tsc across the workspace
pnpm check # biome lint + format check
pnpm sync-pets # copy repo-root pets/ into each app's public assets
pnpm encode-demos # re-derive docs/assets/*.mp4 + poster from the GIFs (needs ffmpeg)
pnpm test:e2e # Playwright, desktop only
pnpm test:path-hook # the installer's PATH edit, against a scratch registry key
pnpm release:bump <major|minor|patch|X.Y.Z> # one version across every manifest, committed and tagged
Modules
| Path | What it owns | Docs |
|---|---|---|
apps/desktop |
Tauri shell, pet windows, agent event ingress | apps/desktop/AGENTS.md |
crates/pets-driven-core |
Authoritative Pet + Registered Working Directory state behind a repository seam | crates/AGENTS.md |
crates/pets-driven-fs |
Shared on-disk state.v1.json repository with a cross-process file lock |
crates/AGENTS.md |
crates/pets-driven-protocol |
Hook-forwarding wire contract (routes, synthesized event) | crates/AGENTS.md |
crates/pets-driven-cli |
The pdd CLI: direct state ops + live hook forwarding |
crates/AGENTS.md |
apps/web |
Landing site + Remotion demo video | apps/web/AGENTS.md |
packages/pet-engine |
ECS simulation, personalities, sprite state | packages/pet-engine/AGENTS.md |
packages/design-system |
Tokens and shared React components | packages/design-system/AGENTS.md |
packages/i18n |
Locales, i18next setup, translation catalog | packages/i18n/AGENTS.md |
plugins/pets-driven |
Shared Claude Code + Codex plugin: hooks, commands, skills | — |
pets/ |
Canonical built-in pet definitions and spritesheets | pets/README.md |
scripts/ |
Asset sync, version bump, install test | — |
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.
- yesterday First seen · 78 lines · 1,500 tokens per session scan A e9cb1c7142f2
pets-driven AGENTS.md is an instructions file published in the GitHub repository young1the/pets-driven (1 stars, last pushed 2d ago), licensed MIT. It adds 1,500 tokens to every session, about $0.0075 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-31.
Other instructions, from other repositories
agent-toolkit AGENTS.md
Instructions for DiUS/agent-toolkit, covering agents.md, what this repo is, repo map, principles and how to add each component type.
agent-toolkit CLAUDE.md
Instructions for DiUS/agent-toolkit, covering claude.md, claude code specifics, testing changes locally, load the plugin from this working tree and preview skill discovery for the npx-skills channel.
codex-mcp AGENTS.md
AGENTS.md instructions for workspace-json/codex-mcp: This repository ships workspace.json intelligence to coding agents. When you work in a project that has it installed, follow the same discipline the tooling enforces.
agent-harness AGENTS.md
AGENTS.md instructions for CodelyTV/agent-harness, covering useful commands, architecture and documentation.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).