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-status/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-status)<a href="https://agentmods.dev/skills/helixdevelopment/code/speckit-superspec-status"><img src="https://agentmods.dev/badge/skills/helixdevelopment/code/speckit-superspec-status/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-status"><img src="https://agentmods.dev/badge/skills/helixdevelopment/code/speckit-superspec-status.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.00551 |
| Opus 5 | $0.00011 | $0.00275 |
| Sonnet 5 | $0.00004 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
speckit-superspec-status 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.status
Show current project progress, feature status, and superpowers detection results.
Usage
/speckit.superspec.status [spec-number|all]
Process
- Scan
.specify/directory structure - Check if
constitution.mdexists - Run superpowers detection: Check for all superpowers skills at
.agents/skills/and~/.agents/skills/. Update.specify/superpowers.ymlwith current detection results. - For each spec directory, read
progress.yml(or infer progress from existing files) - Display a status summary:
Superspec Project Status
========================
Constitution: Done (2026-04-22)
Superpowers: brainstorming (detected), writing-plans (not found)
Features:
001-user-auth [####------] execute (Phase 5/6) — T012/T019 tasks done
002-photo-upload [##--------] brainstorm (Phase 2/6) — 2 open questions
003-settings [#---------] specify (Phase 1/6) — draft
Suggested next step: /speckit.superspec.execute 001
- If no
.specify/exists, suggest: "No superspec project found. Run/speckit.constitutionto get started."
File Inference Fallback
If progress.yml does not exist, infer progress from which files are present:
spec.mdexists → specify is donespec.mdhas Brainstorm Log entries → brainstorm was runplan.mdexists → plan is donetasks.mdexists → tasks are donetasks.mdhas[x]checkboxes → execute is in progress (count checked vs total)
Superpowers Detection
Check for skills at these paths:
.agents/skills/{skill-name}/SKILL.md(project-local)~/.agents/skills/{skill-name}/SKILL.md(user-global)
Results are persisted to .specify/superpowers.yml. See .specify/extensions/superspec/references/superpowers-bridge.md
for full detection and adaptation details.
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 · 64 lines · 22 tokens per session scan A 61a2d9f339cc
speckit-superspec-status 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 551 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
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent - run one issue/PR pipeline on one repository as a supervised fleet. Auto-pick items, preflight every candidate to one deterministic claim verdict, stand up one worker session per item in a dedicated folder, probe them each cycle with one script call…
feature-request
Conversational workflow for gathering user feedback and filing GitHub Issues on the Kiro Crew repository. Load when the user clicks "Request a Feature", wants to report a bug, or suggest an improvement.
goal-loop
Bootstrap a goal-driven self-improving AutoNudge loop from a goal plus an anchor directory, then run the board autonomously until the Definition of Done is met.
vigilante-create-issue
Help a human author write an implementation-ready GitHub issue that Vigilante can execute reliably.
vigilante-issue-implementation
Implement a GitHub issue end-to-end when Vigilante dispatches work for a watched repository. Use the provided worktree, respect repository instructions, comment on the issue as work progresses, and report failures back to GitHub.