Borrowing it
Nothing to install: this file belongs to reinhardhq/claude-code-spec-boilerplate. 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/reinhardhq/claude-code-spec-boilerplate/main/.claude/commands/kiro:init.mdgit clone --depth 1 https://github.com/reinhardhq/claude-code-spec-boilerplateWrote 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/reinhardhq/claude-code-spec-boilerplate/kiro-init)<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/kiro-init"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/kiro-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/reinhardhq/claude-code-spec-boilerplate/kiro-init"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/kiro-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.00346 |
| Opus 5 | $0.00000 | $0.00173 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
kiro: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 9d 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
kiro:init - Claude Code Spec-Driven Development セットアップ
このコマンドは、Claude Code Spec-Driven Developmentのファイルを現在のプロジェクトにセットアップします。
実行内容
-
.claude/commands/kiro/ディレクトリの作成とコマンドのコピー- claude-code-specプロジェクトから全てのkiroコマンドをコピー
-
CLAUDE.mdファイルのコピー
- claude-code-specからCLAUDE.mdをコピー（既存ファイルがある場合はバックアップ）
-
初期ディレクトリ構造の作成
.kiro/steering/- ステアリング文書用.kiro/specs/- 機能仕様用
使用方法
/kiro:init
処理フロー
- 現在のプロジェクトディレクトリを確認
- claude-code-specプロジェクトの場所を確認（
/Users/reinhardhq/app-projects/claude-code-spec） - 必要なディレクトリを作成
- コマンドファイルをコピー
- CLAUDE.mdをコピー（既存の場合はバックアップ）
- セットアップ完了メッセージを表示
注意事項
- 既存のCLAUDE.mdは
CLAUDE.md.backupとして保存されます - 既存のkiroコマンドは上書きされます
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.
- 9d ago First seen · 33 lines · 0 tokens per session scan A 57971a8b5ec6
kiro:init is a command published in the GitHub repository reinhardhq/claude-code-spec-boilerplate (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 346 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.
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.