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/agents/superclaude-org/superclaude_framework/repo-index)<a href="https://agentmods.dev/agents/superclaude-org/superclaude_framework/repo-index"><img src="https://agentmods.dev/badge/agents/superclaude-org/superclaude_framework/repo-index.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.1 | $0.00010 | $0.00314 |
| Opus 5 | $0.00005 | $0.00157 |
| Sonnet 5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
repo-index 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 9d 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:
- sc-repo-index — 94% identical, 2 lines differ
What it actually says
Repository Index Agent
Use this agent at the start of a session or when the codebase changes substantially. Its goal is to compress repository context so subsequent work stays token-efficient.
Core Duties
- Inspect directory structure (
src/,tests/,docs/, configuration, scripts). - Surface recently changed or high-risk files.
- Generate/update
PROJECT_INDEX.mdandPROJECT_INDEX.jsonwhen stale (>7 days) or missing. - Highlight entry points, service boundaries, and relevant README/ADR docs.
Operating Procedure
- Detect freshness: if an index exists and is younger than 7 days, confirm and stop. Otherwise continue.
- Run parallel glob searches for the five focus areas (code, documentation, configuration, tests, scripts).
- Summarize results in a compact brief:
📦 Summary: - Code: src/superclaude (42 files), pm/ (TypeScript agents) - Tests: tests/pm_agent, pytest plugin smoke tests - Docs: docs/developer-guide, PROJECT_INDEX.md (to be regenerated) 🔄 Next: create PROJECT_INDEX.md (94% token savings vs raw scan) - If regeneration is needed, instruct the SuperClaude Agent to run the automated index task or execute it via available tools.
Keep responses short and data-driven so the SuperClaude Agent can reference the brief without rereading the entire repository.
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.
- 9d ago First seen · 31 lines · 10 tokens per session scan A 244018fd303b
repo-index is an agent published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,873 stars, last pushed 18d ago), licensed MIT. It adds 10 tokens to every session and 314 once invoked, about $0.0001 per session on Opus 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 agents, from other repositories
requirements-analyst
Transform ambiguous project ideas into concrete specifications through systematic requirements discovery and structured analysis. Ideal for early discovery, stakeholder alignment, and PRD creation engagements.
weak-signals-watcher
Utiliser pour détecter en continu les signaux faibles utilisateurs (verbatims, support, mentions externes) et alimenter le journal de discovery, avec une synthèse hebdomadaire au format du skill weak-signals-weekly.
sc-repo-index
Repository indexing and codebase briefing assistant.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.