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.
npx agentmods add instructions/superclaude-org/superclaude_plugin/claude-mdgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_PluginWrote 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/instructions/superclaude-org/superclaude_plugin/claude-md)<a href="https://agentmods.dev/instructions/superclaude-org/superclaude_plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/superclaude-org/superclaude_plugin/claude-md.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 | $0.00514 | $0.00514 |
| Opus 5 | $0.00257 | $0.00257 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
SuperClaude_Plugin CLAUDE.md 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SuperClaude Plugin
This plugin provides the complete SuperClaude framework as a native Claude Code plugin.
Components Included
Commands (35 total)
- 25 /sc: commands: Full workflow automation from brainstorming to deployment
- 10 /kiro: commands: Spec-driven development with TDD methodology
Agents (21 total)
- 15 specialized agents: Technical expertise across domains
- 6 Context Engineering agents: Advanced context optimization
Behavioral Modes (7 modes)
- Brainstorming, Business Panel, Deep Research, Orchestration
- Token Efficiency, Task Management, Introspection
Core Framework
- PRINCIPLES.md: Software engineering philosophy
- RULES.md: Behavioral rules and decision trees
- FLAGS.md: Mode activation and control flags
- BUSINESS_PANEL_EXAMPLES.md: Strategic analysis examples
- BUSINESS_SYMBOLS.md: Symbol communication system
Installation
For complete installation instructions, see README.md.
Quick Install
/plugin marketplace add SuperClaude-Org/SuperClaude_Plugin
/plugin install sc@superclaude
After installation, restart Claude Code to activate the plugin.
Quick Start
After installation, restart Claude Code and try:
# See all available commands
/sc:help
# Start a new project
/sc:brainstorm "your project idea"
# Analyze codebase
/sc:analyze
# Deep research
/sc:research "your topic"
Documentation
For complete documentation, visit SuperClaude Documentation
Migration from pip/npm
If you previously installed SuperClaude via pip or npm, you can safely uninstall those versions:
# Uninstall pip version
pip uninstall SuperClaude
# Uninstall npm version
npm uninstall -g @bifrost_inc/superclaude
The plugin version provides the same functionality with easier installation and updates.
Support
- 🐛 Issues: GitHub Issues
- 💬 Discussions: GitHub Discussions
- 📖 Documentation: SuperClaude Docs
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.
- 5d ago First seen · 84 lines · 514 tokens per session scan A 46d2069bcd4e
SuperClaude_Plugin CLAUDE.md is an instructions file published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 15d ago), licensed MIT. It adds 514 tokens to every session, about $0.0026 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).