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/kaze-jp/kusa/spec-statusgit clone --depth 1 https://github.com/kaze-jp/kusaWrote 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/kaze-jp/kusa/spec-status)<a href="https://agentmods.dev/commands/kaze-jp/kusa/spec-status"><img src="https://agentmods.dev/badge/commands/kaze-jp/kusa/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.00464 |
| Opus 5 | $0.00000 | $0.00232 |
| Sonnet 5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00046 |
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 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
Show Spec Status
Display the current status of a feature specification, including phase completion and progress.
Usage
/kiro:spec-status <feature-name>
Instructions
-
Locate the spec directory at
.kiro/specs/$FEATURE_NAME/. If it does not exist, report that no spec exists for this feature. -
Check each phase by looking for the corresponding files:
Phase File Status Init requirements-init.mdExists? Requirements requirements.mdExists? Design design.mdExists? Tasks tasks.mdExists? Implementation (check task completion) Progress? -
If
tasks.mdexists, analyze implementation progress:- Count total tasks
- Count completed tasks (checked acceptance criteria)
- Count parallelizable tasks remaining
- Identify current blockers (tasks with unmet dependencies that are not complete)
- Calculate percentage complete
-
Check for blockers:
- Open questions in any document
- Tasks marked as blocked
- Design gaps noted during implementation
-
Generate a status report:
# Spec Status: <feature-name>
## Phase Progress
- [x] Init (requirements-init.md)
- [x] Requirements (requirements.md)
- [x] Design (design.md)
- [ ] Tasks (tasks.md)
- [ ] Implementation
## Current Phase: <phase-name>
<Details about what needs to happen next>
## Implementation Progress (if applicable)
- Total tasks: X
- Completed: Y / X (Z%)
- Parallelizable remaining: N
- Blocked: M
## Blockers
- <blocker description>
## Next Steps
- <recommended next action>
- Display the report to the user.
Output
- Status report displayed to the user (not written to a file)
Notes
- If no feature name is provided, list all specs found in
.kiro/specs/with their statuses. - This command is read-only; it does not modify any files.
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 · 75 lines · 0 tokens per session scan A 7a28c643c998
spec-status is a command published in the GitHub repository kaze-jp/kusa (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 464 tokens. 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.