Borrowing it
Nothing to install: this file belongs to j5ik2o/okite-ai. 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/j5ik2o/okite-ai/main/.codex/prompts/kiro-spec-init.mdgit clone --depth 1 https://github.com/j5ik2o/okite-aiWrote 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/j5ik2o/okite-ai/kiro-spec-init)<a href="https://agentmods.dev/commands/j5ik2o/okite-ai/kiro-spec-init"><img src="https://agentmods.dev/badge/commands/j5ik2o/okite-ai/kiro-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/j5ik2o/okite-ai/kiro-spec-init"><img src="https://agentmods.dev/badge/commands/j5ik2o/okite-ai/kiro-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.00662 |
| Opus 5 | $0.00000 | $0.00331 |
| Sonnet 5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
kiro-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 7d 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
84% identical to spec-init — 21 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Initialization
<background_information>
- Mission: Initialize the first phase of spec-driven development by creating directory structure and metadata for a new specification
- Success Criteria:
- Generate appropriate feature name from project description
- Create unique spec structure without conflicts
- Provide clear path to next phase (requirements generation) </background_information>
Execution Steps
- Check Uniqueness: Verify
.kiro/specs/for naming conflicts (append number suffix if needed) - Create Directory:
.kiro/specs/[feature-name]/ - Initialize Files Using Templates:
- Read
.kiro/settings/templates/specs/init.json - Read
.kiro/settings/templates/specs/requirements-init.md - Replace placeholders:
{{FEATURE_NAME}}→ generated feature name{{TIMESTAMP}}→ current ISO 8601 timestamp{{PROJECT_DESCRIPTION}}→ $ARGUMENTS
- Write
spec.jsonandrequirements.mdto spec directory
- Read
Important Constraints
- DO NOT generate requirements/design/tasks at this stage
- Follow stage-by-stage development principles
- Maintain strict phase separation
- Only initialization is performed in this phase
Tool Guidance
- Use Glob to check existing spec directories for name uniqueness
- Use Read to fetch templates:
init.jsonandrequirements-init.md - Use Write to create spec.json and requirements.md after placeholder replacement
- Perform validation before any file write operation
Output Description
Provide output in the language specified in spec.json with the following structure:
- Generated Feature Name:
feature-nameformat with 1-2 sentence rationale - Project Summary: Brief summary (1 sentence)
- Created Files: Bullet list with full paths
- Next Step: Command block showing
/prompts:kiro-spec-requirements <feature-name> - Notes: Explain why only initialization was performed (2-3 sentences on phase separation)
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.
- 7d ago First seen · 68 lines · 0 tokens per session scan A 90501fcb1619
kiro-spec-init is a command published in the GitHub repository j5ik2o/okite-ai (81 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 662 tokens. A static security scan graded it A with 0 findings. It is 84% identical to spec-init, differing in 21 lines, and is treated as a copy.
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.