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_plugin/sc-spec-panelgit 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/commands/superclaude-org/superclaude_plugin/sc-spec-panel)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-spec-panel"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-spec-panel.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.1 | $0.00017 | $0.03631 |
| Opus 5 | $0.00009 | $0.01816 |
| Sonnet 5 | $0.00003 | $0.00726 |
| Haiku 4.5 | $0.00002 | $0.00363 |
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 6d 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.
This is a copy
98% identical to spec-panel — 36 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:sc: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: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.
- 6d ago First seen · 436 lines · 17 tokens per session scan A 5f439f27fa1a
spec-panel is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 15d ago), licensed MIT. It adds 17 tokens to every session and 3,631 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to spec-panel, differing in 36 lines, and is treated as a copy.
Other commands, from other repositories
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.
stats
Show statistics about the Reality Check database.
mpm-postmortem
Analyze session errors and suggest improvements.