Borrowing it
Nothing to install: this file belongs to kaze-jp/kusa. 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/kaze-jp/kusa/main/.claude/commands/kiro/spec-init.mdgit 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-init)<a href="https://agentmods.dev/commands/kaze-jp/kusa/spec-init"><img src="https://agentmods.dev/badge/commands/kaze-jp/kusa/spec-init/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/kaze-jp/kusa/spec-init"><img src="https://agentmods.dev/badge/commands/kaze-jp/kusa/spec-init.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.00000 | $0.00572 |
| Opus 5.5 | $0.00000 | $0.00229 |
| Sonnet 5.5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
spec-init 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Feature Spec
Initialize a new feature specification directory and generate initial requirements.
Usage
/kiro:spec-init <feature-name>
Instructions
-
Worktree guard — Before anything else, check if you are working in a git worktree (not on the main/master branch). If you are on the main branch, stop and create a worktree first using the
superpowers:using-git-worktreesskill orgit worktree add. Do NOT proceed with spec initialization until you are in an isolated worktree. -
Read product context from
.ao/steering/product.mdif it exists. Use this to understand the product vision, target users, and strategic goals. -
Create the spec directory at
.kiro/specs/$FEATURE_NAME/. -
Gather feature information by asking the user:
- What is the feature's purpose?
- Who are the target users?
- What problem does it solve?
- Are there any known constraints?
-
Generate
requirements-init.mdin the spec directory with the following structure:
# Feature: <feature-name>
## Overview
<Brief description of the feature and its purpose>
## Product Context
<Relevant context from product.md>
## Initial Requirements
### Functional Requirements
<List requirements using EARS format>
### Non-Functional Requirements
<Performance, security, accessibility requirements using EARS format>
### Constraints
<Known constraints and limitations>
### Assumptions
<Assumptions made during requirements gathering>
### Open Questions
<Questions that need answers before proceeding>
-
Apply EARS format for all requirements:
- Ubiquitous: "The shall "
- Event-driven: "When , the shall "
- State-driven: "While , the shall "
- Optional: "Where , the shall "
- Unwanted: "If , the shall "
-
Confirm with the user that the initial requirements capture their intent before finalizing.
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.
- 2mo ago First seen · 74 lines · 0 tokens per session scan A f1f880a3d984
spec-init is a command published in the GitHub repository kaze-jp/kusa (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 572 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.