Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/moorestech/moorestech/kiro-spec-statusgit clone --depth 1 https://github.com/moorestech/moorestechWrote 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/moorestech/moorestech/kiro-spec-status)<a href="https://agentmods.dev/commands/moorestech/moorestech/kiro-spec-status"><img src="https://agentmods.dev/badge/commands/moorestech/moorestech/kiro-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 | $0.00000 | $0.00651 |
| Opus 5 | $0.00000 | $0.00326 |
| Sonnet 5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
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 2d 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
89% identical to spec-status — 16 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.
- 2d ago First seen · 88 lines · 0 tokens per session scan A a849a41566ba
kiro-spec-status is a command published in the GitHub repository moorestech/moorestech (82 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 651 tokens. A static security scan graded it A with 0 findings. It is 89% identical to spec-status, differing in 16 lines, and is treated as a copy.
Other commands, from other repositories
make-avaloniaui-custom-control
HTML/CSS to AvaloniaUI AXAML conversion command.
dotnet-review
Multi-agent .NET code review - up to five reviewers in parallel (correctness, performance, security/observability, data/messaging/integration, generalist), then an adversarial maintainer pass that refutes weak findings. Runs the bundled dotnet-review workflow; reviewer model scales with change size.
dumpstack
Helps examine thread call stacks. While clrstack is more commonly used for managed call stacks, dumpstack can also be used to inspect stack frames, including native ones.
name2ee
Displays the MethodTable and MethodDesc structures for a specified method or type name.
security
Scan a .NET project for security vulnerabilities and dependency health issues.
git
Git operations with intelligent commit messages and workflow optimization.