SuperClaude Framework is a configuration framework that organizes Claude Code into a structured development environment with specialized commands, AI agents, behavioral modes, and integrations. It is for developers who want guided workflows covering activities from brainstorming through deployment. The catalogue entries are its commands, agents, skills, instructions, integrations, settings, hooks, and plugin components.
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.
git clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_FrameworkWrote 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_framework/pm)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_framework/pm"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/pm/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/commands/superclaude-org/superclaude_framework/pm"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/pm.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.00020 | $0.04806 |
| Opus 5.5 | $0.00008 | $0.01922 |
| Sonnet 5.5 | $0.00004 | $0.00961 |
| Haiku 4.5 | $0.00002 | $0.00481 |
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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pm — 100% identical, 28 lines differ
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: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:pm [request] [--strategy brainstorm|direct|wave] [--verbose]
# Override to specific sub-agent (optional)
/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.
- 1mo ago First seen · 593 lines · 20 tokens per session scan A 36e91e86a5b4
pm is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,905 stars, last pushed 20d ago), licensed MIT. It adds 20 tokens to every session and 4,806 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
automation
Manage durable recurring session automations through the daemon API.
report
Persist a meaningful worker report for durable delivery to the active project orchestrator.
import
Import reads the legacy Agent Orchestrator flat-file store (/.agent-orchestrator) read-only and ports its projects and per-project settings into the rewrite database. Legacy files are never modified, and a re-run skips rows that already exist, so it is safe to run more than once. The daemon must be stopped before…
story-6.1.4
Story ID: 6.1.4 Epic: Epic-6.1 - Agent Identity System Wave: Wave 1 (Foundation) Status: 📋 Ready to Start Priority: 🔴 Critical Owner: Dev (Dex) Created: 2025-01-14 Updated: 2025-01-17 (v4 - Unified System Integration) Duration: 2.5 days (20 hours) Investment: $250.00.
story-7.1.1
Story ID: 7.1.1 Epic: Epic-7 - Dashboard Workspace Integration Wave: Wave 1 (Foundation) Status: ⌛ In Progress Priority: 🔴 High Owner: Architect (Aria) → Dev (Dex) Created: 2026-05-05 Updated: 2026-05-05.