Borrowing it
Nothing to install: this file belongs to gaoconggit/SharpPad. 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/gaoconggit/SharpPad/main/.claude/commands/kiro/spec-status.mdgit clone --depth 1 https://github.com/gaoconggit/SharpPadWrote 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/gaoconggit/sharppad/spec-status)<a href="https://agentmods.dev/commands/gaoconggit/sharppad/spec-status"><img src="https://agentmods.dev/badge/commands/gaoconggit/sharppad/spec-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/commands/gaoconggit/sharppad/spec-status"><img src="https://agentmods.dev/badge/commands/gaoconggit/sharppad/spec-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.00005 | $0.00720 |
| Opus 5.5 | $0.00002 | $0.00288 |
| Sonnet 5.5 | $0.00001 | $0.00144 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
spec-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 13d 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
84% identical to spec-status — 7 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specification Status
Show current status and progress for feature: $1
Spec Context
Spec Files
- Spec directory: !
ls -la .kiro/specs/$1/ - Spec metadata:
.kiro/specs/$1/spec.json - Requirements:
.kiro/specs/$1/requirements.md - Design:
.kiro/specs/$1/design.md - Tasks:
.kiro/specs/$1/tasks.md
All Specs Overview
- Available specs: !
ls -la .kiro/specs/ - Active specs: !
find .kiro/specs/ -name "spec.json" -exec grep -l "implementation_ready.*true" {} \;
Task: Generate Status Report
Create comprehensive status report for the specification in the language specified in spec.json (check .kiro/specs/$1/spec.json for "language" field):
1. Specification Overview
Display:
- Feature name and description
- Creation date and last update
- Current phase (requirements/design/tasks/implementation)
- Overall completion percentage
2. Phase Status
For each phase, show:
-
✅ Requirements Phase: [completion %]
- Requirements count: [number]
- Acceptance criteria defined: [yes/no]
- Requirements coverage: [complete/partial/missing]
-
✅ Design Phase: [completion %]
- Architecture documented: [yes/no]
- Components defined: [yes/no]
- Diagrams created: [yes/no]
- Integration planned: [yes/no]
-
✅ Tasks Phase: [completion %]
- Total tasks: [number]
- Completed tasks: [number]
- Remaining tasks: [number]
- Blocked tasks: [number]
3. Implementation Progress
If in implementation phase:
- Task completion breakdown
- Current blockers or issues
- Estimated time to completion
- Next actions needed
Task Completion Tracking
- Parse tasks.md checkbox status:
- [x](completed) vs- [ ](pending) - Count completed vs total tasks
- Show completion percentage
- Identify next uncompleted task
4. Quality Metrics
Show:
- Requirements coverage: [percentage]
- Design completeness: [percentage]
- Task granularity: [appropriate/too large/too small]
- Dependencies resolved: [yes/no]
5. Recommendations
Based on status, provide:
- Next steps to take
- Potential issues to address
- Suggested improvements
- Missing elements to complete
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.
- 13d ago First seen · 98 lines · 5 tokens per session scan A fe23d897909f
spec-status is a command published in the GitHub repository gaoconggit/SharpPad (83 stars, last pushed 7mo ago), licensed MIT. It adds 5 tokens to every session and 720 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 84% identical to spec-status, differing in 7 lines, and is treated as a copy.
Other commands, from other repositories
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.
project-principles
Define your project's non-negotiable principles, commitments, and boundaries.
fast
⚡⚡⚡ Quickly bootstrap a new project automatically.
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
shortlist
Select and prioritize MVP features from an existing backlog.