What is kiro-spec-status?

A status checker for a Kiro specification, a set of project files that describes requirements, design, and implementation tasks.

Use it to review requirements, design, task completion, approvals, and links between related project work.

It shows what phase is complete, what remains, and which blockers or approvals may need attention.

How akaghef/M3E configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to akaghef/M3E. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/akaghef/M3E/main/.agents/skills/kiro-spec-status/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/akaghef/M3E

Made for: Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/akaghef/m3e/kiro-spec-status/github.svg)](https://agentmods.dev/skills/akaghef/m3e/kiro-spec-status)

Your own site

<a href="https://agentmods.dev/skills/akaghef/m3e/kiro-spec-status"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/kiro-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/akaghef/m3e/kiro-spec-status"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/kiro-spec-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 675 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 88% copy Near-identical to another mod in the catalogue.

Token cost

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.00010	$0.00675
Opus 5.5	$0.00004	$0.00270
Sonnet 5.5	$0.00002	$0.00135
Haiku 4.5	$0.00001	$0.00068

Measured 5d ago against content hash 5c7abdaa0ad5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

kiro-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 5d 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.

Origin

This is a copy

88% identical to kiro-spec-status — 19 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.

.agents/skills/kiro-spec-status/SKILL.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Specification Status

<background_information>

Success Criteria:
- Show current phase and completion status
- Identify next actions and blockers
- Provide clear visibility into progress
- Surface boundary readiness, upstream/downstream context, and likely revalidation needs when available </background_information>

Step 1: Load Spec Context

Read .kiro/specs/$1/spec.json for metadata and phase status
Read .kiro/specs/$1/brief.md if it exists
Read existing files: requirements.md, design.md, tasks.md (if they exist)
Check .kiro/specs/$1/ directory for available files
Read .kiro/steering/roadmap.md if it exists and this spec appears in it

Step 2: Analyze Status

Parse each phase:

Requirements: Count requirements and acceptance criteria
Design: Check for architecture, components, diagrams, and whether boundary sections are present
Tasks: Count completed vs total tasks (parse - [x] vs - [ ])
Approvals: Check approval status in spec.json
Boundary context:
- From brief.md: note Boundary Candidates, Upstream / Downstream, and Existing Spec Touchpoints if present
- From design.md: note Boundary Commitments, Out of Boundary, Allowed Dependencies, and Revalidation Triggers if present
- From roadmap.md: note upstream dependencies and whether this spec is adjacent to Existing Spec Updates
Revalidation watchlist:
- Identify downstream specs, neighboring existing-spec updates, or rollout-sensitive design notes that may need revalidation if this spec changes
- Call out when the current spec shape looks too broad and may want roadmap/design splitting instead of more local repair

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
Boundary Context: Upstream/downstream, out-of-boundary, and allowed dependency notes when available
Revalidation Watchlist: Downstream or adjacent work likely affected by changes to this spec
Next Actions: What needs to be done next
Blockers: Any issues preventing progress

Read the full file on GitHub · 72 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

agents/openai.yaml 147 B

Changes

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.

5d ago First seen · 72 lines · 10 tokens per session scan A 5c7abdaa0ad5

Subscribe to this mod's changes

kiro-spec-status is a skill published in the GitHub repository akaghef/M3E (11 stars, last pushed 5d ago), licensed MIT. It adds 10 tokens to every session and 675 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to kiro-spec-status, differing in 19 lines, and is treated as a copy.

Project management

story-readiness

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

Donchitos/Claude-Code-Game-Studios · 35 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

M3E: Skill for Codex