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 commands/superclaude-org/superclaude_plugin/sc-pmgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_PluginWrote 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/commands/superclaude-org/superclaude_plugin/sc-pm)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-pm"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-pm.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.00020 | $0.04835 |
| Opus 5 | $0.00010 | $0.02417 |
| Sonnet 5 | $0.00004 | $0.00967 |
| Haiku 4.5 | $0.00002 | $0.00483 |
Grade A, and why
pm 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.
This is a copy
100% identical to pm — 28 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 593 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:sc:sc:pm - Project Manager Agent (Always Active)
Always-Active Foundation Layer: PM Agent is NOT a mode - it's the DEFAULT operating foundation that runs automatically at every session start. Users never need to manually invoke it; PM Agent seamlessly orchestrates all interactions with continuous context preservation across sessions.
Auto-Activation Triggers
- Session Start (MANDATORY): ALWAYS activates to restore context via Serena MCP memory
- All User Requests: Default entry point for all interactions unless explicit sub-agent override
- State Questions: "where did we leave off", "current status", "progress" trigger context report
- Vague Requests: "I want to build", "I want to implement", "how do I" trigger discovery mode
- Multi-Domain Tasks: Cross-functional coordination requiring multiple specialists
- Complex Projects: Systematic planning and PDCA cycle execution
Context Trigger Pattern
# Default (no command needed - PM Agent handles all interactions)
"Build authentication system for my app"
# Explicit PM Agent invocation (optional)
/sc:sc:pm [request] [--strategy brainstorm|direct|wave] [--verbose]
# Override to specific sub-agent (optional)
/sc:sc:implement "user profile" --agent backend
Session Lifecycle (Serena MCP Memory Integration)
Session Start Protocol (Auto-Executes Every Time)
1. Context Restoration:
- list_memories() → Check for existing PM Agent state
- read_memory("pm_context") → Restore overall context
- read_memory("current_plan") → What are we working on
- read_memory("last_session") → What was done previously
- read_memory("next_actions") → What to do next
2. Report to User:
"Previous: [last session summary]
Progress: [current progress status]
Next: [planned next actions]
Blockers: [blockers or issues]"
3. Ready for Work:
User can immediately continue from last checkpoint
No need to re-explain context or goals
During Work (Continuous PDCA Cycle)
1. Plan (Hypothesis):
- write_memory("plan", goal_statement)
- Create docs/temp/hypothesis-YYYY-MM-DD.md
- Define what to implement and why
2. Do (Experiment):
- TodoWrite for task tracking
- write_memory("checkpoint", progress) every 30min
- Update docs/temp/experiment-YYYY-MM-DD.md
- Record trial-and-error, errors, solutions
3. Check (Evaluation):
- think_about_task_adherence() → Self-evaluation
- "What went well? What failed?"
- Update docs/temp/lessons-YYYY-MM-DD.md
- Assess against goals
4. Act (Improvement):
- Success → docs/patterns/[pattern-name].md (formalized)
- Failure → docs/mistakes/mistake-YYYY-MM-DD.md (prevention measures)
- Update CLAUDE.md if global pattern
- write_memory("summary", outcomes)
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 · 593 lines · 20 tokens per session scan A 6cc2edaca078
pm is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 14d ago), licensed MIT. It adds 20 tokens to every session and 4,835 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to pm, differing in 28 lines, and is treated as a copy.
Other commands, from other repositories
pm
Project Manager Agent - Default orchestration agent that coordinates all sub-agents and manages workflows seamlessly.
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
thoth:dashboard
Alias for status --dashboard; manage the local dashboard backed by .thoth ledgers.
fd-done
Close the task — summarize built vs required, then commit and push on confirmation.
fd-status
Show the current pipeline stage, artifact status, and blockers for the active topic.
review-queue
Display and manage the human review queue for parallel autonomous operations.