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_framework/agents-mdgit 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/instructions/superclaude-org/superclaude_framework/agents-md)<a href="https://agentmods.dev/instructions/superclaude-org/superclaude_framework/agents-md"><img src="https://agentmods.dev/badge/instructions/superclaude-org/superclaude_framework/agents-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.00651 | $0.00651 |
| Opus 5 | $0.00326 | $0.00326 |
| Sonnet 5 | $0.00130 | $0.00130 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
SuperClaude_Framework AGENTS.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 4d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/superclaude/holds the Python package and pytest plugin entrypoints.tests/contains Python integration/unit suites; markers map to features inpyproject.toml.pm/,research/, andindex/house TypeScript agents with standalonepackage.json.skills/holds runtime skills (e.g.,confidence-check);commands/documents scripted Claude commands.docs/provides reference packs; start withdocs/developer-guidefor workflow expectations.
Build, Test, and Development Commands
make installinstalls the framework editable viauv pip install -e ".[dev]".make testrunsuv run pytestacrosstests/.make doctorormake verifycheck CLI wiring and plugin health.make lintandmake formatdelegate to Ruff; run after significant edits.- TypeScript agents: inside
pm/, runnpm installonce, thennpm testornpm run build; repeat forresearch/andindex/.
Coding Style & Naming Conventions
- Python: 4-space indentation, Black line length 88, Ruff
E,F,I,N,W; prefer snake_case for modules/functions and PascalCase for classes. - Keep pytest markers explicit (
@pytest.mark.unit, etc.) and match file namestest_*.py. - TypeScript: rely on project
tsconfig.json; keep filenames kebab-case and exported classes PascalCase; align with existing PM agent modules. - Reserve docstrings or inline comments for non-obvious orchestration; let clear naming do the heavy lifting.
Testing Guidelines
- Default to
make test; adduv run pytest -m unitto scope runs during development. - When changes touch CLI or plugin startup, extend integration coverage in
tests/test_pytest_plugin.py. - Respect coverage focus on
src/superclaude(tool.coverage.run); adjust configuration instead of skipping logic. - For TypeScript agents, add Jest specs under
__tests__/*.test.tsand keep coverage thresholds satisfied vianpm run test:coverage.
Commit & Pull Request Guidelines
- Follow Conventional Commits (
feat:,fix:,refactor:) as seen ingit log; keep present-tense summaries under ~72 chars. - Group related file updates per commit to simplify bisects and release notes.
- Before opening a PR, run
make lint,make format, andmake test; include summaries of verification steps in the PR description. - Reference linked issues (
Closes #123) and, for agent workflow changes, add brief reproduction notes; screenshots only when docs change. - Tag reviewers listed in
CODEOWNERSwhen touching owned directories.
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.
- 4d ago First seen · 39 lines · 651 tokens per session scan A d4d74c0ba3a0
SuperClaude_Framework AGENTS.md is an instructions file published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,868 stars, last pushed 13d ago), licensed MIT. It adds 651 tokens to every session, about $0.0033 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.