Borrowing it
Nothing to install: this file belongs to j5ik2o/okite-ai. 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/j5ik2o/okite-ai/main/.claude/commands/kiro/spec-status.mdgit clone --depth 1 https://github.com/j5ik2o/okite-aiWrote 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/j5ik2o/okite-ai/spec-status)<a href="https://agentmods.dev/commands/j5ik2o/okite-ai/spec-status"><img src="https://agentmods.dev/badge/commands/j5ik2o/okite-ai/spec-status.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.00005 | $0.00659 |
| Opus 5 | $0.00003 | $0.00329 |
| Sonnet 5 | $0.00001 | $0.00132 |
| Haiku 4.5 | $0.00001 | $0.00066 |
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 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
91% identical to spec-status — 10 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specification Status
<background_information>
- Mission: Display comprehensive status and progress for a specification
- Success Criteria:
- Show current phase and completion status
- Identify next actions and blockers
- Provide clear visibility into progress </background_information>
Execution Steps
Step 1: Load Spec Context
- Read
.kiro/specs/$1/spec.jsonfor metadata and phase status - Read existing files:
requirements.md,design.md,tasks.md(if they exist) - Check
.kiro/specs/$1/directory for available files
Step 2: Analyze Status
Parse each phase:
- Requirements: Count requirements and acceptance criteria
- Design: Check for architecture, components, diagrams
- Tasks: Count completed vs total tasks (parse
- [x]vs- [ ]) - Approvals: Check approval status in spec.json
Step 3: Generate Report
Create report in the language specified in spec.json covering:
- Current Phase & Progress: Where the spec is in the workflow
- Completion Status: Percentage complete for each phase
- Task Breakdown: If tasks exist, show completed/remaining counts
- Next Actions: What needs to be done next
- Blockers: Any issues preventing progress
Critical Constraints
- Use language from spec.json
- Calculate accurate completion percentages
- Identify specific next action commands
Tool Guidance
- Read: Load spec.json first, then other spec files as needed
- Parse carefully: Extract completion data from tasks.md checkboxes
- Use Glob to check which spec files exist
Output Description
Provide status report in the language specified in spec.json:
Report Structure:
- Feature Overview: Name, phase, last updated
- Phase Status: Requirements, Design, Tasks with completion %
- Task Progress: If tasks exist, show X/Y completed
- Next Action: Specific command to run next
- Issues: Any blockers or missing elements
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 · 88 lines · 5 tokens per session scan A 8ab7fe114a9f
spec-status is a command published in the GitHub repository j5ik2o/okite-ai (81 stars, last pushed 4mo ago), licensed MIT. It adds 5 tokens to every session and 659 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to spec-status, differing in 10 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.