Borrowing it
Nothing to install: this file belongs to HelixDevelopment/code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/HelixDevelopment/code/main/.specify/extensions/superspec/.specify-dev/agent-commands/claude/speckit-superspec-review/SKILL.mdgit clone --depth 1 https://github.com/HelixDevelopment/codeWrote 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/skills/helixdevelopment/code/speckit-superspec-review)<a href="https://agentmods.dev/skills/helixdevelopment/code/speckit-superspec-review"><img src="https://agentmods.dev/badge/skills/helixdevelopment/code/speckit-superspec-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/helixdevelopment/code/speckit-superspec-review"><img src="https://agentmods.dev/badge/skills/helixdevelopment/code/speckit-superspec-review.svg" alt="Reviewed on agentmods" width="80" 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.00022 | $0.00461 |
| Opus 5 | $0.00011 | $0.00230 |
| Sonnet 5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
speckit-superspec-review 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.
What it actually says
speckit.superspec.review
Run code review against spec requirements using review skills.
Usage
/speckit.superspec.review [scope]
Scope: Optional file paths, spec number, or "all changes". Defaults to the latest feature.
Process
- Read the spec and plan for the feature being reviewed
- Superpowers detection: Check for
requesting-code-reviewskill- If found: Read the skill and follow its pre-evaluation checklist and review dispatch protocol
- If not found: Use the built-in review protocol below
- Built-in review protocol:
- Spec compliance: Verify each acceptance scenario from the spec is implemented
- Edge case coverage: Verify brainstormed edge cases are handled
- Constitution compliance: Check all governance principles are respected
- Code quality: Check for bugs, security issues, error handling
- Test coverage: Verify tests exist for critical paths
- Report findings with confidence scores (0-100, only report issues >= 80)
- Group findings by severity: Critical > Important > Suggestion
Output
Review findings reported to user. Optionally written to
specs/NNN-feature-name/checklist-review.md.
Finding Format
Each finding includes:
- Clear description with confidence score
- File path and line reference
- Specific recommendation or fix suggestion
Findings below 80 confidence are suppressed to reduce noise.
Superpowers Adaptation
When using the requesting-code-review skill, adapt its outputs:
- Add superspec-specific review dimensions: spec compliance, constitution compliance, brainstorm coverage
- Output location → report to user, optionally write to checklist file
See .specify/extensions/superspec/references/superpowers-bridge.md for full adaptation rules.
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 · 60 lines · 22 tokens per session scan A 095da1559e74
speckit-superspec-review is a skill published in the GitHub repository HelixDevelopment/code (2 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 461 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-09-04.
Other skills, from other repositories
hqe
Comprehensive codebase health auditing, remediation, and verification skill based on the canonical HQE Protocol v5.0.0.
simplify-code
Sequential 3-lens cleanup of recent code changes.
hunk-extensions
Maps the hunkdiff/extension authoring surface for Hunk, the terminal diff viewer — hiding or reordering reviewed files, docked panes, alternate file views, commands and key bindings, dialogs, workspace writes, themes, syntax languages, VCS backends, lifecycle events. Use when writing, debugging, or installing a Hunk…
sage-review
Deep, platform-neutral code review for PRs and CRs in ONE thorough single pass — design reasoning (Problem Worth Solving & Solution Fit) as one dimension alongside the 9 code-level dimensions, with chain-of-consequences, self-critique, and draft-only comments. The single app-owned source of truth.
rubber-duck
Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.