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/ruizrica/toolkit/kirogit clone --depth 1 https://github.com/ruizrica/toolkitWrote 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/ruizrica/toolkit/kiro)<a href="https://agentmods.dev/commands/ruizrica/toolkit/kiro"><img src="https://agentmods.dev/badge/commands/ruizrica/toolkit/kiro.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.00911 |
| Opus 5 | $0.00000 | $0.00456 |
| Sonnet 5 | $0.00000 | $0.00182 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
kiro 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 3d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/kiro
Spec-driven development workflow that generates professional requirements, design, and task documentation using the Kiro methodology, then executes with parallel agents.
Usage
/kiro [feature idea] [--project PATH] [--name SPEC_NAME] [--agent cursor|haiku]
Arguments
| Argument | Required | Description |
|---|---|---|
| feature idea | Yes | Description of the feature to implement |
| --project PATH | No | Project path (defaults to current directory) |
| --name SPEC_NAME | No | Spec name (defaults to date-based format) |
| --agent cursor|haiku | No | Agent type for execution (default: cursor) |
Workflow Phases
The Kiro workflow has 4 interactive phases, each pausing for clarifying questions:
Phase 1: Requirements Generation
- Spawns 2 Haiku agents to gather context (domain exploration, constraints discovery)
- Generates EARS-format requirements document
- Pauses for Q&A: scope, users, constraints, priorities
Phase 2: Design Generation
- Spawns 2 Haiku agents (architecture designer, API designer)
- Generates comprehensive design document
- Pauses for Q&A: architecture approval, technology choices, trade-offs
Phase 3: Tasks Generation
- Spawns 2 Haiku agents (task decomposer, test planner)
- Generates implementation task breakdown
- Pauses for Q&A: task granularity, implementation order, scope
Phase 4: Execution
- Parses tasks into dependency waves
- Executes with parallel agents (4 Cursor or Haiku agents)
- Follows TDD approach (test first)
- Reports completion summary
Document Storage
All documents are saved to ~/.claude/plans/{spec_name}/:
~/.claude/plans/2026-02-01-user-authentication/
├── 1-requirements.md # EARS format requirements
├── 2-design.md # Architecture, components, APIs
├── 3-tasks.md # Implementation task breakdown
├── qa-log.md # Clarifying questions and answers
└── metadata.json # Spec metadata, phase status
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.
- 3d ago First seen · 131 lines · 0 tokens per session scan A 08ca3042fd05
kiro is a command published in the GitHub repository ruizrica/toolkit (5 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 911 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
git
Git operations with intelligent commit messages and workflow optimization.
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.