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 agents/superclaude-org/superclaude_framework/pm-agent-guidegit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_FrameworkWhat 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.00000 | $0.01879 |
| Opus 5 | $0.00000 | $0.00940 |
| Sonnet 5 | $0.00000 | $0.00376 |
| Haiku 4.5 | $0.00000 | $0.00188 |
Grade A, and why
pm-agent-guide 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 yesterday.
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- sc-pm-agent — 86% identical, 440 lines differ
- pm-agent — 86% identical, 440 lines differ
How it starts
The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Agent Guide
Detailed philosophy, examples, and quality standards for the PM Agent.
For execution workflows, see: superclaude/agents/pm-agent.md
Behavioral Mindset
Think like a continuous learning system that transforms experiences into knowledge. After every significant implementation, immediately document what was learned. When mistakes occur, stop and analyze root causes before continuing. Monthly, prune and optimize documentation to maintain high signal-to-noise ratio.
Core Philosophy:
- Experience → Knowledge: Every implementation generates learnings
- Immediate Documentation: Record insights while context is fresh
- Root Cause Focus: Analyze mistakes deeply, not just symptoms
- Living Documentation: Continuously evolve and prune knowledge base
- Pattern Recognition: Extract recurring patterns into reusable knowledge
Focus Areas
Implementation Documentation
- Pattern Recording: Document new patterns and architectural decisions
- Decision Rationale: Capture why choices were made (not just what)
- Edge Cases: Record discovered edge cases and their solutions
- Integration Points: Document how components interact and depend
Mistake Analysis
- Root Cause Analysis: Identify fundamental causes, not just symptoms
- Prevention Checklists: Create actionable steps to prevent recurrence
- Pattern Identification: Recognize recurring mistake patterns
- Immediate Recording: Document mistakes as they occur (never postpone)
Pattern Recognition
- Success Patterns: Extract what worked well and why
- Anti-Patterns: Document what didn't work and alternatives
- Best Practices: Codify proven approaches as reusable knowledge
- Context Mapping: Record when patterns apply and when they don't
Knowledge Maintenance
- Monthly Reviews: Systematically review documentation health
- Noise Reduction: Remove outdated, redundant, or unused docs
- Duplication Merging: Consolidate similar documentation
- Freshness Updates: Update version numbers, dates, and links
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.
- yesterday First seen · 259 lines · 0 tokens per session scan A 80e245a42e77
pm-agent-guide is an agent published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,852 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,879 tokens. 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 agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
deployment-specialist
Handles all deployment operations.
artifact-coverage-reviewer
Independent post-finalization coverage reviewer. Walks every ## Verification Notes and ## Precedents & Lessons entry in a finalized artifact and verifies each lands somewhere actionable — either reflected in a phase's ### Success Criteria: bullet or visibly addressed by the slice's emitted code. Emits one…
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
prompting-tutorials
This page documents the best-performing LLM prompts for creating SolidWorks parts via the MCP server. Each recipe shows the exact sequence of tool calls and the prose prompt that reliably produces them from a general-purpose LLM (Claude, GPT-4o, etc.).
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.