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/git)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_framework/git"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/git/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/git"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/git.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.00011 | $0.00494 |
| Opus 5.5 | $0.00004 | $0.00198 |
| Sonnet 5.5 | $0.00002 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
git 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:
- git — 97% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:git - Git Operations
Triggers
- Git repository operations: status, add, commit, push, pull, branch
- Need for intelligent commit message generation
- Repository workflow optimization requests
- Branch management and merge operations
Usage
/sc:git [operation] [args] [--smart-commit] [--interactive]
Behavioral Flow
- Analyze: Check repository state and working directory changes
- Validate: Ensure operation is appropriate for current Git context
- Execute: Run Git command with intelligent automation
- Optimize: Apply smart commit messages and workflow patterns
- Report: Provide status and next steps guidance
Key behaviors:
- Generate conventional commit messages based on change analysis
- Apply consistent branch naming conventions
- Handle merge conflicts with guided resolution
- Provide clear status summaries and workflow recommendations
Tool Coordination
- Bash: Git command execution and repository operations
- Read: Repository state analysis and configuration review
- Grep: Log parsing and status analysis
- Write: Commit message generation and documentation
Key Patterns
- Smart Commits: Analyze changes → generate conventional commit message
- Status Analysis: Repository state → actionable recommendations
- Branch Strategy: Consistent naming and workflow enforcement
- Error Recovery: Conflict resolution and state restoration guidance
Examples
Smart Status Analysis
/sc:git status
# Analyzes repository state with change summary
# Provides next steps and workflow recommendations
Intelligent Commit
/sc:git commit --smart-commit
# Generates conventional commit message from change analysis
# Applies best practices and consistent formatting
Interactive Operations
/sc:git merge feature-branch --interactive
# Guided merge with conflict resolution assistance
Boundaries
Will:
- Execute Git operations with intelligent automation
- Generate conventional commit messages from change analysis
- Provide workflow optimization and best practice guidance
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 · 80 lines · 11 tokens per session scan A 4bccf0abad49
git is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,905 stars, last pushed 20d ago), licensed MIT. It adds 11 tokens to every session and 494 once invoked, about $0.0000 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
git
Git operations with intelligent commit messages and workflow optimization.
cg-mac-release
Build, sign, notarize, and publish a macOS app as a GitHub release with a professional DMG.
git
Git operations with intelligent commit messages and workflow optimization.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.