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/build)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_framework/build"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/build/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/build"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/build.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.00015 | $0.00659 |
| Opus 5.5 | $0.00006 | $0.00264 |
| Sonnet 5.5 | $0.00003 | $0.00132 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
build 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:
- build — 94% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:build - Project Building and Packaging
Triggers
- Project compilation and packaging requests for different environments
- Build optimization and artifact generation needs
- Error debugging during build processes
- Deployment preparation and artifact packaging requirements
Usage
/sc:build [target] [--type dev|prod|test] [--clean] [--optimize] [--verbose]
Behavioral Flow
- Analyze: Project structure, build configurations, and dependency manifests
- Validate: Build environment, dependencies, and required toolchain components
- Execute: Build process with real-time monitoring and error detection
- Optimize: Build artifacts, apply optimizations, and minimize bundle sizes
- Package: Generate deployment artifacts and comprehensive build reports
Key behaviors:
- Configuration-driven build orchestration with dependency validation
- Intelligent error analysis with actionable resolution guidance
- Environment-specific optimization (dev/prod/test configurations)
- Comprehensive build reporting with timing metrics and artifact analysis
MCP Integration
- Playwright MCP: Auto-activated for build validation and UI testing during builds
- DevOps Engineer Persona: Activated for build optimization and deployment preparation
- Enhanced Capabilities: Build pipeline integration, performance monitoring, artifact validation
Tool Coordination
- Bash: Build system execution and process management
- Read: Configuration analysis and manifest inspection
- Grep: Error parsing and build log analysis
- Glob: Artifact discovery and validation
- Write: Build reports and deployment documentation
Key Patterns
- Environment Builds: dev/prod/test → appropriate configuration and optimization
- Error Analysis: Build failures → diagnostic analysis and resolution guidance
- Optimization: Artifact analysis → size reduction and performance improvements
- Validation: Build verification → quality gates and deployment readiness
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 · 94 lines · 15 tokens per session scan A e99ca14da8db
build is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,905 stars, last pushed 20d ago), licensed MIT. It adds 15 tokens to every session and 659 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
troubleshoot
Diagnose and resolve issues in code, builds, deployments, and system behavior.
analyze
Comprehensive code analysis across quality, security, performance, and architecture domains.
10_gofer_cloud
Deploy and configure the Gofer cloud integration for remote pipeline execution.
7a_stakeholder_comms
Generate stakeholder-facing communications: release notes, demo scripts, and change briefs.
9_gofer_tests
Generate comprehensive test suites from four testing perspectives for a target component.
gofer_hydrate
Reverse-engineer specification from existing code (Hydration).