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/jasonkneen/kiro/create-steering-documentsgit clone --depth 1 https://github.com/jasonkneen/kiroWrote 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/jasonkneen/kiro/create-steering-documents)<a href="https://agentmods.dev/commands/jasonkneen/kiro/create-steering-documents"><img src="https://agentmods.dev/badge/commands/jasonkneen/kiro/create-steering-documents.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.1 | $0.00000 | $0.01274 |
| Opus 5 | $0.00000 | $0.00637 |
| Sonnet 5 | $0.00000 | $0.00255 |
| Haiku 4.5 | $0.00000 | $0.00127 |
Grade A, and why
create-steering-documents 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 6d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Steering Documents
Create comprehensive steering documents for a development project based on the project type and requirements.
Usage
Create steering documents for [project description]
Examples
Create steering documents for a React TypeScript e-commerce applicationCreate steering documents for a Python Django REST API with PostgreSQLCreate steering documents for a Node.js microservices architectureCreate steering documents for a Vue.js component library
Process
You are an expert at creating project steering documents that provide contextual guidance for development work. Follow this systematic approach:
1. Project Analysis
First, analyze the project requirements and determine which steering documents are needed:
For Frontend Projects (React, Vue, Angular):
- Include: project-standards.md, git-workflow.md, frontend-standards.md, development-environment.md
- Consider: component-library.md, testing-strategy.md
For Backend/API Projects (Node.js, Python, Java):
- Include: project-standards.md, git-workflow.md, api-design.md, development-environment.md
- Consider: database-standards.md, security-guidelines.md
For Full-Stack Projects:
- Include: All core documents plus technology-specific ones
- Consider: deployment-standards.md, monitoring-guidelines.md
For Library/Package Projects:
- Include: project-standards.md, git-workflow.md, documentation-standards.md
- Consider: versioning-strategy.md, publishing-guidelines.md
2. Document Creation Strategy
Create steering documents using these templates and guidelines:
Core Documents (Always Create)
project-standards.md - #[[file:.kiro/steering/project-standards.md]]
- Adapt code quality standards to project language/framework
- Customize testing requirements based on project complexity
- Include project-specific documentation needs
- Set security practices relevant to the domain
git-workflow.md - #[[file:.kiro/steering/git-workflow.md]]
- Adjust branch naming for team size and release strategy
- Customize commit message format for project needs
- Set appropriate review requirements
- Define merge strategies
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.
- 6d ago First seen · 158 lines · 0 tokens per session scan A bce9ea254f5f
create-steering-documents is a command published in the GitHub repository jasonkneen/kiro (746 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,274 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-30.
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.