sc:index-repo

sc:index-repo is a command for Claude Code from SuperClaude-Org/SuperClaude_Framework. It costs 22 tokens per session (773 once invoked), scanned A, original, MIT.

A command for creating a compact index of a software repository. A repository is the project folder containing source code, documentation, configuration, tests, and tools.

In plain words
What is it for?
Use it to summarize the project structure, entry points, public functions and classes, APIs, dependencies, tests, and scripts in PROJECT_INDEX.md.
Why use it?
It gives future sessions a short overview to read instead of scanning every file, reducing the amount of project text they need to process.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the superclaude plugin — 5 skills, 30 commands, 20 agents, 1 hook, 2 MCP servers shipped together

Good fit Use it to summarize the project structure, entry points, public functions and classes, APIs, dependencies, tests, and scripts in PROJECT_INDEX.md.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/superclaude-org/superclaude_framework/index-repo
About the project

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.

SuperClaude-Org/SuperClaude_Framework · 23,876 stars · on GitHub · superclaude.netlify.app

Install

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.

Clone the repo
git clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_Framework

Made for: Claude Code.

Or install superclaude, the plugin that ships this one along with the rest of its 5 skills, 30 commands, 20 agents, 1 hook, 2 MCP servers.

Wrote 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.

agentmods badge for sc:index-repo

README.md
[![agentmods](https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/index-repo/github.svg)](https://agentmods.dev/commands/superclaude-org/superclaude_framework/index-repo)
Your own site
<a href="https://agentmods.dev/commands/superclaude-org/superclaude_framework/index-repo"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/index-repo/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.

agentmods 80×15 button for sc:index-repo

Your own site · 80×15
<a href="https://agentmods.dev/commands/superclaude-org/superclaude_framework/index-repo"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/index-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 773 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.00773
Opus 5 $0.00011 $0.00387
Sonnet 5 $0.00004 $0.00155
Haiku 4.5 $0.00002 $0.00077

Measured 10d ago against content hash fc4e204a2f52, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

sc:index-repo 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 10d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/superclaude/commands/index-repo.md · 166 lines

How it starts

The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Index Creator

📊 Index Creator activated

Problem Statement

Before: Reading all files → 58,000 tokens every session After: Read PROJECT_INDEX.md → 3,000 tokens (94% reduction)

Index Creation Flow

Phase 1: Analyze Repository Structure

Parallel analysis (5 concurrent Glob searches):

  1. Code Structure

    src/**/*.{ts,py,js,tsx,jsx}
    lib/**/*.{ts,py,js}
    superclaude/**/*.py
    
  2. Documentation

    docs/**/*.md
    *.md (root level)
    README*.md
    
  3. Configuration

    *.toml
    *.yaml, *.yml
    *.json (exclude package-lock, node_modules)
    
  4. Tests

    tests/**/*.{py,ts,js}
    **/*.test.{ts,py,js}
    **/*.spec.{ts,py,js}
    
  5. Scripts & Tools

    scripts/**/*
    bin/**/*
    tools/**/*
    

Phase 2: Extract Metadata

For each file category, extract:

  • Entry points (main.py, index.ts, cli.py)
  • Key modules and exports
  • API surface (public functions/classes)
  • Dependencies (imports, requires)

Phase 3: Generate Index

Create PROJECT_INDEX.md with structure:

# Project Index: {project_name}

Generated: {timestamp}

## 📁 Project Structure

{tree view of main directories}

## 🚀 Entry Points

- CLI: {path} - {description}
- API: {path} - {description}
- Tests: {path} - {description}

## 📦 Core Modules

### Module: {name}
- Path: {path}
- Exports: {list}
- Purpose: {1-line description}

## 🔧 Configuration

- {config_file}: {purpose}

## 📚 Documentation

- {doc_file}: {topic}

## 🧪 Test Coverage

- Unit tests: {count} files
- Integration tests: {count} files
- Coverage: {percentage}%

## 🔗 Key Dependencies

- {dependency}: {version} - {purpose}

## 📝 Quick Start

1. {setup step}
2. {run step}
3. {test step}

Phase 4: Validation

Quality checks:

  • All entry points identified?
  • Core modules documented?
  • Index size < 5KB?
  • Human-readable format?

Usage

Create index:

/index-repo

Update existing index:

/index-repo mode=update

Read the full file on GitHub · 166 lines

Changes

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.

  1. 10d ago First seen · 166 lines · 22 tokens per session scan A fc4e204a2f52

Subscribe to this mod's changes

sc:index-repo is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,876 stars, last pushed 19d ago), licensed MIT. It adds 22 tokens to every session and 773 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.