Borrowing it
Nothing to install: this file belongs to yaowenhu-pm/ai-product-playbook. 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/yaowenhu-pm/ai-product-playbook/main/AGENTS.mdgit clone --depth 1 https://github.com/yaowenhu-pm/ai-product-playbookWrote 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/yaowenhu-pm/ai-product-playbook/agents-md)<a href="https://agentmods.dev/instructions/yaowenhu-pm/ai-product-playbook/agents-md"><img src="https://agentmods.dev/badge/instructions/yaowenhu-pm/ai-product-playbook/agents-md/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/instructions/yaowenhu-pm/ai-product-playbook/agents-md"><img src="https://agentmods.dev/badge/instructions/yaowenhu-pm/ai-product-playbook/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00534 | $0.00534 |
| Opus 5 | $0.00267 | $0.00267 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
ai-product-playbook 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 7d 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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository publishes a VitePress online book. Numbered chapters live in model/, platform/, and applications/. Reusable, unnumbered assets live in toolkit/; concise supporting examples live in cases/. Do not create duplicate article bodies under book/ or elsewhere. scripts/generate-content-index.mjs scans those directories and generates the VitePress index plus the marked catalogue in README.md. Theme code is in .vitepress/theme/, site configuration in .vitepress/config.ts, and the visit counter Worker in workers/visit-counter.js with wrangler.jsonc.
Build, Test, and Development Commands
npm run docs:dev— regenerate the content index and start local development.npm run docs:build— regenerate the index and build.vitepress/dist; run before every commit.npm run docs:preview— serve the existing production build locally.npx wrangler deploy— deploy the visit-counter Worker only when its code or configuration changes.git diff --check— catch whitespace errors before committing.
There is no separate test suite. A successful npm run docs:build, correct generated chapter count, and a manual check of changed links are the required validation baseline.
Content, Style, and Naming
Keep filenames numbered and kebab-cased, for example platform/03-agent-reliability.md; the generator defines reading order from filenames. Preserve each article's first-level title, section marker, and 撰写日期 line. Write public-facing Chinese that is restrained, specific, and professional; remove internal credentials, private operational details, chat transcripts, and implementation details that do not change a reader's future decision. Edit navigation rules in scripts/generate-content-index.mjs, not generated files under .vitepress/generated/.
Commits, Pull Requests, and Deployment
Use concise Conventional-Commit-style prefixes when applicable: feat:, fix:, docs:, or style:. Keep each commit focused. Pull requests should state the reader-facing change, list validation commands, and include screenshots for visual/theme changes. Pushing eligible paths to main triggers GitHub Pages; the workflow also runs a daily build-and-deploy check at 11:00 Beijing time.
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.
- 7d ago Changed · +17 tokens per session 1179e6e030e4
- 11d ago First seen · 28 lines · 517 tokens per session scan A 9ab8da99c324
ai-product-playbook AGENTS.md is an instructions file published in the GitHub repository yaowenhu-pm/ai-product-playbook (10 stars, last pushed 10d ago), licensed MIT. It adds 534 tokens to every session, about $0.0027 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
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.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).