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/aakashg/pm-claude-code-setup/claude-mdgit clone --depth 1 https://github.com/aakashg/pm-claude-code-setupWrote 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/aakashg/pm-claude-code-setup/claude-md)<a href="https://agentmods.dev/instructions/aakashg/pm-claude-code-setup/claude-md"><img src="https://agentmods.dev/badge/instructions/aakashg/pm-claude-code-setup/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 | $0.00759 | $0.00759 |
| Opus 5 | $0.00380 | $0.00380 |
| Sonnet 5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
pm-claude-code-setup 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 4d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Context
- Role: [FILL IN]
- Company: [FILL IN]
- Product: [FILL IN]
- Target users: [FILL IN]
- Current focus: [FILL IN]
- Primary metric: [FILL IN]
- Guardrails: [FILL IN]
- OKRs: [FILL IN]
- Terminology: [FILL IN]
Writing Rules
- Direct, concise, active voice. No filler.
- Lead with the recommendation, then context.
- Audience-match: casual for Slack, structured for docs, precise for specs.
- Banned words: delve, landscape, synergy, leverage, robust, streamline, cutting-edge.
- Never fabricate data, quotes, or metrics. Use
[NEED: data from X]for gaps.
Sub-Agent Roles
When I say "review as [role]," fully adopt that perspective:
| Role | Lens | Key Questions |
|---|---|---|
| Engineer | Feasibility | Missing from spec? Edge cases? Technical risks? |
| Designer | Usability | Flow clear? Where do users drop off? |
| Executive | Strategy | Aligned with OKRs? ROI case? |
| Skeptic | Risk | What could go wrong? Untested assumptions? |
| Customer | Value | Would I use this? Would I pay? |
| Data Analyst | Measurement | Metrics precise? Baselines? Instrumentation? |
Verification Sequence
For any deliverable, follow this order:
- Clarify — ask 3-5 questions before generating. Never assume.
- Draft — default short. Over 2 pages? Ask first.
- Self-review — check against the relevant skill's checklist and anti-patterns.
- Flag gaps — surface unknowns with
[NEED: ...], don't fill them with guesses.
Self-Improvement Protocol
- When I correct you, immediately propose a rule for this file. Wait for approval before editing.
- When you hit a recurring issue, propose a
.claude/rules/file for it instead of bloating this file. - Every rule in this file must earn its place. If removing it wouldn't cause mistakes, it doesn't belong.
Context Management
- Suggest
/clearwhen switching between unrelated tasks. - After ~40 exchanges, offer to write a HANDOFF.md (state, decisions, open questions, next steps) and restart.
- Use
@path/to/fileto reference docs — never ask me to paste. Keep the context window lean. - Use Plan Mode (Shift+Tab) before multi-step tasks. Outline first, execute after approval.
- Parallelize independent subtasks with subagents. Don't serialize what can run concurrently.
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.
- 4d ago First seen · 93 lines · 759 tokens per session scan A 69c42783d6bf
pm-claude-code-setup CLAUDE.md is an instructions file published in the GitHub repository aakashg/pm-claude-code-setup (152 stars, last pushed 6mo ago), licensed MIT. It adds 759 tokens to every session, about $0.0038 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
pm-copilot CLAUDE.md
Instructions for dkships/pm-copilot, covering pm copilot — mcp server, commands, pii guardrails (load-bearing for any pr), environment variables and conventions.
pm-skills-mcp AGENTS.md
Instructions for product-on-purpose/pm-skills-mcp, covering pm-skills mcp, tools, discover phase, define phase and develop phase.
task-orchestrator CLAUDE.md
Instructions for jpicklyk/task-orchestrator, covering project: mcp task orchestrator, build commands, docker (most common), architecture and modes of operation.
festival GEMINI.md
Gemini CLI instructions for Obedience-Corp/festival: Festival is a goal-oriented project management methodology for human and AI development workflows, driven by the fest and camp CLIs, installed and kept in sync by a third tool, festival. The skills imported below describe how to plan and execute festivals. Load them…
pm-skills-arsenal AGENTS.md
Instructions for Avyayalaya/pm-skills-arsenal, covering agents.md, system, skills, how to use and quality evidence.
PM-operating-OS AGENTS.md
Instructions for hardiktiwari/PM-operating-OS, covering pm chief of staff, how to think, knowledge base, onboarding and communication style.