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:help.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-help)<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/kiro-help"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/kiro-help/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-help"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/kiro-help.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.00011 | $0.01401 |
| Opus 5 | $0.00005 | $0.00700 |
| Sonnet 5 | $0.00002 | $0.00280 |
| Haiku 4.5 | $0.00001 | $0.00140 |
Grade A, and why
kiro:help 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 8d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kiro Help - Spec-Driven Development Workflow
This command provides comprehensive guidance on using the Kiro specification-driven development system.
What is Kiro?
Kiro is a specification-driven development framework that helps you build software features through a systematic, phase-based approach. It ensures proper documentation, planning, and review before implementation begins.
Workflow Overview
The Kiro workflow follows these phases in order:
graph TD
A[Phase 0: Steering<br>/kiro:steering] -->|Optional| B[Phase 1: Initialize Project<br>/kiro:init]
B --> C[Phase 2: Create Spec<br>/kiro:spec-init]
C --> D[Phase 3: Generate Requirements<br>/kiro:spec-requirements]
D --> E[Phase 4: Create Design<br>/kiro:spec-design]
E --> F[Phase 5: Plan Tasks<br>/kiro:spec-tasks]
F --> G[Phase 6: Implementation<br>Start coding!]
style A fill:#e1f5fe
style G fill:#c8e6c9
Command Reference
Phase 0: Steering (Optional)
Commands:
/kiro:steering- Create/update standard steering documents/kiro:steering-custom- Create custom steering for specialized contexts
Purpose: Establish project context and constraints. Optional for new features or small additions.
Creates:
.kiro/steering/product.md- Product overview and business context.kiro/steering/tech.md- Technology stack and development environment.kiro/steering/structure.md- Project structure and architectural patterns
Phase 1: Project Initialization
Command: /kiro:init
Purpose: Initialize the Kiro system in your project with example specifications.
Creates:
.kiro/directory structure- Example specifications for learning
- Initial project setup
Phase 2: Specification Initialization
Command: /kiro:spec-init [detailed description]
Purpose: Initialize a new feature specification based on your detailed project description.
Example:
/kiro:spec-init Create a user authentication system with email/password login, JWT tokens, password reset functionality, and role-based access control
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.
- 8d ago First seen · 197 lines · 11 tokens per session scan A ab1fb0be46ea
kiro:help is a command published in the GitHub repository reinhardhq/claude-code-spec-boilerplate (2 stars, last pushed 1y ago), licensed MIT. It adds 11 tokens to every session and 1,401 once invoked, about $0.0001 per session on Opus 5. 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.