Borrowing it
Nothing to install: this file belongs to j5ik2o/event-store-adapter-js. 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/event-store-adapter-js/main/.claude/commands/kiro/steering.mdgit clone --depth 1 https://github.com/j5ik2o/event-store-adapter-jsWrote 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/event-store-adapter-js/steering)<a href="https://agentmods.dev/commands/j5ik2o/event-store-adapter-js/steering"><img src="https://agentmods.dev/badge/commands/j5ik2o/event-store-adapter-js/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.00012 | $0.00961 |
| Opus 5 | $0.00006 | $0.00481 |
| Sonnet 5 | $0.00002 | $0.00192 |
| Haiku 4.5 | $0.00001 | $0.00096 |
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.
This is a copy
83% identical to kiro-steering — 36 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kiro Steering Management
<background_information>
Role: Maintain .kiro/steering/ as persistent project memory.
Mission:
- Bootstrap: Generate core steering from codebase (first-time)
- Sync: Keep steering and codebase aligned (maintenance)
- Preserve: User customizations are sacred, updates are additive
Success Criteria:
- Steering captures patterns and principles, not exhaustive lists
- Code drift detected and reported
- All
.kiro/steering/*.mdtreated equally (core + custom) </background_information>
Check .kiro/steering/ status:
Bootstrap Mode: Empty OR missing core files (product.md, tech.md, structure.md) Sync Mode: All core files exist
Bootstrap Flow
- Load templates from
.kiro/settings/templates/steering/ - Analyze codebase (JIT):
glob_file_searchfor source filesread_filefor README, package.json, etc.grepfor patterns
- Extract patterns (not lists):
- Product: Purpose, value, core capabilities
- Tech: Frameworks, decisions, conventions
- Structure: Organization, naming, imports
- Generate steering files (follow templates)
- Load principles from
.kiro/settings/rules/steering-principles.md - Present summary for review
Focus: Patterns that guide decisions, not catalogs of files/dependencies.
Sync Flow
- Load all existing steering (
.kiro/steering/*.md) - Analyze codebase for changes (JIT)
- Detect drift:
- Steering → Code: Missing elements → Warning
- Code → Steering: New patterns → Update candidate
- Custom files: Check relevance
- Propose updates (additive, preserve user content)
- Report: Updates, warnings, recommendations
Update Philosophy: Add, don't replace. Preserve user sections.
Granularity Principle
From .kiro/settings/rules/steering-principles.md:
"If new code follows existing patterns, steering shouldn't need updating."
Document patterns and principles, not exhaustive lists.
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 · 144 lines · 12 tokens per session scan A 7aa7ae977349
steering is a command published in the GitHub repository j5ik2o/event-store-adapter-js (24 stars, last pushed 3d ago), licensed Apache-2.0. It adds 12 tokens to every session and 961 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to kiro-steering, differing in 36 lines, and is treated as a copy.
Other commands, from other repositories
add-business-rule
../../.ai/prompts/add-business-rule.prompt.md.
add-concept
../../.ai/prompts/add-concept.prompt.md.
add-ef-migration
../../.ai/prompts/add-ef-migration.prompt.md.
add-projection
../../.ai/prompts/add-projection.prompt.md.
add-reactor
../../.ai/prompts/add-reactor.prompt.md.
check-doc-drift
../../.ai/prompts/check-doc-drift.prompt.md.