Borrowing it
Nothing to install: this file belongs to kaze-jp/kusa. 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/kaze-jp/kusa/main/.claude/commands/kiro/steering.mdgit clone --depth 1 https://github.com/kaze-jp/kusaWrote 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/kaze-jp/kusa/steering)<a href="https://agentmods.dev/commands/kaze-jp/kusa/steering"><img src="https://agentmods.dev/badge/commands/kaze-jp/kusa/steering.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.00450 |
| Opus 5 | $0.00000 | $0.00225 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
steering 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.
What it actually says
Manage Steering Documents
View and edit the project's steering documents that guide spec generation and implementation.
Usage
/kiro:steering [show|edit <document>]
Instructions
Show Mode (default)
-
Read all steering documents from
.ao/steering/:product.md- Product vision, goals, target userstech.md- Technology stack, patterns, conventionsstructure.md- Project structure and file organization
-
Display a summary of each document:
# Steering Documents
## Product (.ao/steering/product.md)
<First 5-10 lines or key points summary>
Status: Found | Missing
## Tech (.ao/steering/tech.md)
<First 5-10 lines or key points summary>
Status: Found | Missing
## Structure (.ao/steering/structure.md)
<First 5-10 lines or key points summary>
Status: Found | Missing
## Custom Documents
<List any additional .md files in .ao/steering/>
- If any core document is missing, offer to create it with sensible defaults derived from the codebase.
Edit Mode
-
When the user specifies
edit <document>, read the full content of that steering document. -
Present the current content and ask the user what they want to change.
-
Apply the edits as requested by the user.
-
Validate the edited document:
- Ensure it still has required sections
- Check for internal consistency
- Warn if changes conflict with other steering documents
-
Save the updated document and confirm the changes.
Output
- Display of steering document status and content
- Modified steering documents when editing
Notes
- Steering documents are the source of truth for all spec commands.
- Changes to steering documents do not retroactively update existing specs.
- If
.ao/steering/does not exist, create it when the user wants to add a document. - Custom steering documents (added via
/kiro:steering-custom) are also listed here.
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 · 69 lines · 0 tokens per session scan A 503b70ce5630
steering is a command published in the GitHub repository kaze-jp/kusa (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 450 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.