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/exiao/pm-skills/agents-mdgit clone --depth 1 https://github.com/exiao/pm-skillsWrote 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/exiao/pm-skills/agents-md)<a href="https://agentmods.dev/instructions/exiao/pm-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/exiao/pm-skills/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 | $0.00845 | $0.00845 |
| Opus 5 | $0.00423 | $0.00423 |
| Sonnet 5 | $0.00169 | $0.00169 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
pm-skills 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 5d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pm-skills Repo Conventions
A public repo of product/R&D skills for Claude Code, Hermes Agent, Codex, and other skill-aware agents. Every directory at root is a stage of the R&D process (except .github/ and scripts/), and each stage contains related skills.
Repo Structure
stage-name/
├── DESCRIPTION.md # Stage description (with name + description frontmatter)
└── skill-name/
├── SKILL.md # Entry point (required)
├── references/ # Detailed docs, checklists, examples
├── scripts/ # Deterministic code (Python, JS, bash)
└── assets/ # Templates, images, static resources
Stages (the R&D pipeline)
| Stage | What's inside |
|---|---|
| strategy | Diagnose the real obstacle and size up the field: strategy-kernel, competitive-analysis |
| uxr | Understand the user: synthetic-userstudies, journey-mapping |
| pm | Spec and justify: pitch-creator, architecture-diagram |
| design | Make it good: design-review, design-iteration |
| qa | Prove it works: verify-feature, dogfood, adversarial-ux-test |
| launch | Ship and price: launch-strategy, pricing-strategy |
| thinking | Cross-cutting reasoning used at every stage: quick-brainstorm, another-perspective |
Skill Conventions
SKILL.mdmust have YAML frontmatter withnameanddescription.descriptionis a routing instruction for the model, not a human summary. Include trigger phrases.- Keep
SKILL.mdunder 500 lines. Move details toreferences/. - No README.md, CHANGELOG.md, or human-facing docs inside skill directories.
Frontmatter Format
---
name: my-skill
description: What this skill does and when to invoke it. Include trigger phrases.
---
Only name and description are required.
Writing Good Descriptions
The description field is the primary routing signal. When a user says "help me with X," the agent picks a skill based on description match.
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.
- 5d ago First seen · 77 lines · 845 tokens per session scan A d0f7026e06a1
pm-skills AGENTS.md is an instructions file published in the GitHub repository exiao/pm-skills (9 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 845 tokens to every session, about $0.0042 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
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.
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 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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.