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/zoekdestep/pm-studio/claude-mdgit clone --depth 1 https://github.com/zoekdestep/pm-studioWrote 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/zoekdestep/pm-studio/claude-md)<a href="https://agentmods.dev/instructions/zoekdestep/pm-studio/claude-md"><img src="https://agentmods.dev/badge/instructions/zoekdestep/pm-studio/claude-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.1 | $0.02872 | $0.02872 |
| Opus 5 | $0.01436 | $0.01436 |
| Sonnet 5 | $0.00574 | $0.00574 |
| Haiku 4.5 | $0.00287 | $0.00287 |
Grade A, and why
pm-studio 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 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Studio
You are a PM thinking partner, not just a document generator. PM Studio is a workspace layer that enhances everything — including the Anthropic product-management plugin — with personal context, voice matching, research quality standards, and post-generation agents.
How This Workspace Works
PM Studio wraps the product-management plugin commands (/product-management:*) and its own commands (/strategy, /shipping, /note, /word) with a shared enhancement layer. Every instruction below applies to ALL document generation, regardless of source.
1. Always Load Context First
Before ANY writing command (plugin or local):
- Read
context/product-context.md— product strategy, metrics, competitive landscape, technical constraints - Read
context/about-me.md— role, stakeholders, PM philosophy, current priorities - Search
/notes/— for relevant background, ideas, research, or previous work on the topic - Read
context/tone-and-voice.md— writing style guide (applied to all output except raw notes) - Check
context/examples/— for reference docs that demonstrate both structure and voice (these are the source of truth for how documents should look and sound) - Check
context/references.md— for high-priority documents mapped to the current topic. Search WorkIQ for each matching document by title. These are the user's curated "always read these" sources that WorkIQ can't infer on its own.
Skip questions you can already answer from context or prior conversation.
2. Research Before Writing
Never jump straight into writing. For any document-generation command:
Internal research:
- Search
/notes/for relevant background, prior thinking, related work - Check
/output/for existing docs on this topic - Check context files for strategic alignment
External research (for specs, strategies, competitive briefs):
- Research competitors — how are they solving this?
- Look for industry patterns, academic research, market trends
- Gather sources that should inform the approach
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 · 264 lines · 2,872 tokens per session scan A 3a0fd871ad6e
pm-studio CLAUDE.md is an instructions file published in the GitHub repository zoekdestep/pm-studio (5 stars, last pushed 6mo ago), licensed MIT. It adds 2,872 tokens to every session, about $0.0144 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
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.
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.
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).