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 commands/superclaude-org/superclaude_framework/spec-panelgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_FrameworkWhat 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.00017 | $0.03527 |
| Opus 5 | $0.00009 | $0.01764 |
| Sonnet 5 | $0.00003 | $0.00705 |
| Haiku 4.5 | $0.00002 | $0.00353 |
Grade A, and why
spec-panel 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 yesterday.
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:
- spec-panel — 98% identical, 36 lines differ
How it starts
The opening of the file, as written. The whole thing — 428 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:spec-panel - Expert Specification Review Panel
Triggers
- Specification quality review and improvement requests
- Technical documentation validation and enhancement needs
- Requirements analysis and completeness verification
- Professional specification writing guidance and mentoring
Usage
/sc:spec-panel [specification_content|@file] [--mode discussion|critique|socratic] [--experts "name1,name2"] [--focus requirements|architecture|testing|compliance] [--iterations N] [--format standard|structured|detailed]
Behavioral Flow
- Analyze: Parse specification content and identify key components, gaps, and quality issues
- Assemble: Select appropriate expert panel based on specification type and focus area
- Review: Multi-expert analysis using distinct methodologies and quality frameworks
- Collaborate: Expert interaction through discussion, critique, or socratic questioning
- Synthesize: Generate consolidated findings with prioritized recommendations
- Improve: Create enhanced specification incorporating expert feedback and best practices
Key behaviors:
- Multi-expert perspective analysis with distinct methodologies and quality frameworks
- Intelligent expert selection based on specification domain and focus requirements
- Structured review process with evidence-based recommendations and improvement guidance
- Iterative improvement cycles with quality validation and progress tracking
Expert Panel System
Core Specification Experts
Karl Wiegers - Requirements Engineering Pioneer
- Domain: Functional/non-functional requirements, requirement quality frameworks
- Methodology: SMART criteria, testability analysis, stakeholder validation
- Critique Focus: "This requirement lacks measurable acceptance criteria. How would you validate compliance in production?"
Gojko Adzic - Specification by Example Creator
- Domain: Behavior-driven specifications, living documentation, executable requirements
- Methodology: Given/When/Then scenarios, example-driven requirements, collaborative specification
- Critique Focus: "Can you provide concrete examples demonstrating this requirement in real-world scenarios?"
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.
- yesterday First seen · 428 lines · 17 tokens per session scan A 02b57ca07a4e
spec-panel is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,852 stars, last pushed 11d ago), licensed MIT. It adds 17 tokens to every session and 3,527 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 commands, from other repositories
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
analyze
Perform a full 3-stage analysis of a source following the Reality Check methodology.
synthesize
Create a cross-source synthesis across multiple source analyses and claims.
extract
Quick claim extraction from a source without full 3-stage analysis.
validate
Check database integrity and referential consistency.