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/asasugar/superspec/agents-mdgit clone --depth 1 https://github.com/asasugar/SuperSpecWrote 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/asasugar/superspec/agents-md)<a href="https://agentmods.dev/instructions/asasugar/superspec/agents-md"><img src="https://agentmods.dev/badge/instructions/asasugar/superspec/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.02431 | $0.02431 |
| Opus 5 | $0.01215 | $0.01215 |
| Sonnet 5 | $0.00486 | $0.00486 |
| Haiku 4.5 | $0.00243 | $0.00243 |
Grade A, and why
SuperSpec 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 3d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SuperSpec — AI Agent Instructions
🚨 Before ANY Task
- Read configuration:
superspec.config.json→ getlang,specDir,boost,strategy,context - Review project context:
- Read
contextfiles (project rules/conventions) - Check project README, architecture docs, CONTRIBUTING.md
- If no
contextconfigured, auto-check:.cursor/rules/,AGENTS.md,CONTRIBUTING.md
- Read
- Inspect current state:
- Run
/ss-statusor check{specDir}/changes/→ know active changes - Review related changes via
depends_onto avoid duplication
- Run
- Read current change context:
- Determine
strategyby priority: user input-c> config default - Read frontmatter
inputfield → understand original user intent - If
strategy: follow→ treat context files as constraints (must follow) - If
strategy: create→ treat context files as awareness (may deviate, must justify)
- Determine
- Never create change folders manually → use
superspec createCLI or/ss-create
🧭 First Principles
| # | Principle | Rule |
|---|---|---|
| I | Context Economy | < 300 lines per artifact, 400 hard limit. Exceeds → split. Readable in 10 min. |
| II | Signal-to-Noise | Every sentence must inform a decision. If removing it changes nothing → remove it. |
| III | Intent Over Implementation | Focus on why and what. Let how emerge during /ss-apply. |
| IV | Progressive Disclosure | Start minimal. Expand only when clarification demands it. |
| V | Required Sections | Metadata header, Problem, Solution, Success Criteria, Trade-offs. |
🎯 Standard vs Boost
| Standard (lightweight) | Boost (enhanced) | |
|---|---|---|
| 场景 | Simple tasks, bug fixes, small features | Large features, breaking changes, complex designs |
| Artifacts | proposal + checklist + tasks | proposal + spec + checklist + tasks (+ design optional) |
| proposal 定位 | 需求 + 技术方案（自含，可直接拆 task） | 需求背景（Goals, Risks, Impact） |
| spec 定位 | — | 需求细节 + 交互（US/FR/AC/Edge Cases） |
| Checklist 时机 | proposal 后自动检查（/ 10） | spec 后自动检查（/ 25） |
| Task granularity | Flexible | < 1h per task |
| Cross-validation | — | Auto: US↔FR↔AC↔tasks |
| Edge cases | Basic | Comprehensive |
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.
- 3d ago First seen · 211 lines · 2,431 tokens per session scan A bc5c7d615ceb
SuperSpec AGENTS.md is an instructions file published in the GitHub repository asasugar/SuperSpec (15 stars, last pushed 5mo ago), licensed MIT. It adds 2,431 tokens to every session, about $0.0122 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
mstar-harness CLAUDE.md
Instructions for btspoony/mstar-harness, a project described as: An omni-plugin for harness engineering workflows with multi-agents, programmatic gates and skills.
spec-kit-archive copilot-instructions.md
Instructions for stn1slv/spec-kit-archive, covering fixture project — copilot instructions, active technologies and recent changes.
claude-sdd-planner CLAUDE.md
Claude Code instructions for danweinerdev/claude-sdd-planner, covering sdd planner, directory structure, the two-tree architecture, conventions and frontmatter.
leansdd AGENTS.md
Instructions for kidpixo/leansdd, covering agent instructions — spec-driven development, source-of-truth hierarchy (no overlap), single source of truth, file table (read tier · cap) and read workflow (by task type).
claude-sdd-planner AGENTS.md
AGENTS.md instructions for danweinerdev/claude-sdd-planner, covering sdd planner — agent development guide, what this repository is, build and test, editing rules (the ones that bite) and conventions (single sources of truth).
prospec AGENTS.md
Instructions for benwu95/prospec, covering prospec, tech stack, language policy, core resources and constitution.