Borrowing it
Nothing to install: this file belongs to product-on-purpose/pm-skills. 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/product-on-purpose/pm-skills/main/CLAUDE.mdgit clone --depth 1 https://github.com/product-on-purpose/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/product-on-purpose/pm-skills/claude-md)<a href="https://agentmods.dev/instructions/product-on-purpose/pm-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/product-on-purpose/pm-skills/claude-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/product-on-purpose/pm-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/product-on-purpose/pm-skills/claude-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.00568 | $0.00568 |
| Opus 5 | $0.00284 | $0.00284 |
| Sonnet 5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
pm-skills CLAUDE.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 11d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Instructions
Style Rules
No em-dash characters
NEVER use em-dash characters (—, U+2014) in any output. This is a hard rule across all generated content: prose, code comments, file names, commit messages, plan docs, internal notes, memory files, or anything authored by Claude in this repo.
When you would reach for an em-dash, use one of:
-(space-hyphen-space) for parenthetical pauses:(colon) when introducing a clarification or list,(comma) for softer pauses- Sentence break (
.) when the thought completes - Restructure the sentence to remove the need entirely
This rule was codified 2026-04-13 and re-applied through multiple em-dash sweeps. Do not author em-dashes in the first place. The cost of authoring then sweeping is much higher than the cost of internalizing the rule.
Documentation Rules
Public vs Private Files
- Some internal working material is gitignored (for example
_NOTES/,_LOCAL/), so external readers cannot access those paths. Note thatdocs/internal/is TRACKED, not gitignored: it is visible to anyone browsing the repo, so treat it as maintainer-facing rather than private. - Never reference gitignored internal notes in public-facing files:
- README.md
- CHANGELOG.md
- CONTRIBUTING.md
- Any file a user cloning the repo would read
- If content from internal notes needs to be public, move it to a tracked location first
- Agent context files (
_agent-context/) may reference internal notes for coordination
CHANGELOG Best Practices
- Describe what changed, not where your working files are
- Reference public paths only (e.g.,
skills/deliver-prd/) - Link to GitHub issues/PRs for context, not internal planning docs
File References
When referencing files in documentation:
- Use relative paths from repo root
- Only reference tracked (non-gitignored) files
- If a file is gitignored, summarize its content instead of linking
Project Context
- 68 PM skills on main (catalog stable since v2.29.0): 30 phase skills (across 6 Triple Diamond phases) + 11 foundation skills + 12 utility skills + 15 tool-classification entries (Foundation Sprint family of 7 + Design Sprint family of 7 + tool-note-and-vote standalone).
- Follows agentskills.io specification
- Apache 2.0 licensed
- See
AGENTS.mdfor skill discovery
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.
- 11d ago First seen · 50 lines · 568 tokens per session scan A 52c48c59d17e
pm-skills CLAUDE.md is an instructions file published in the GitHub repository product-on-purpose/pm-skills (657 stars, last pushed yesterday), licensed Apache-2.0. It adds 568 tokens to every session, about $0.0028 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-30.
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.
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.