A project-knowledge manager that keeps Markdown files in .kiro/steering/ describing the product, technology choices, and code structure.

Use it to bootstrap project documentation, synchronize steering notes with code changes, and preserve custom guidance.

It helps prevent project knowledge from becoming outdated or scattered. It can create the initial files from a codebase and report when the code and notes no longer match.

How j5ik2o/okite-ai configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/j5ik2o/okite-ai/main/.claude/commands/kiro/steering.md

Clone the repo

git clone --depth 1 https://github.com/j5ik2o/okite-ai

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/j5ik2o/okite-ai/steering/github.svg)](https://agentmods.dev/commands/j5ik2o/okite-ai/steering)

Your own site

<a href="https://agentmods.dev/commands/j5ik2o/okite-ai/steering"><img src="https://agentmods.dev/badge/commands/j5ik2o/okite-ai/steering/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/j5ik2o/okite-ai/steering"><img src="https://agentmods.dev/badge/commands/j5ik2o/okite-ai/steering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 962 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 83% copy Near-identical to another mod in the catalogue.

Token cost

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.00962
Opus 5.5	$0.00005	$0.00385
Sonnet 5.5	$0.00002	$0.00192
Haiku 4.5	$0.00001	$0.00096

Measured 1mo ago against content hash 3a03ef9cdd75, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

Origin

This is a copy

83% identical to kiro-steering — 28 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.

.claude/commands/kiro/steering.md · 144 lines

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/*.md treated 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_search for source files
- read_file for README, package.json, etc.
- grep for 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.

Read the full file on GitHub · 144 lines

Changes

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.

1mo ago First seen · 144 lines · 12 tokens per session scan A 3a03ef9cdd75

Subscribe to this mod's changes

steering is a command published in the GitHub repository j5ik2o/okite-ai (80 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 962 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to kiro-steering, differing in 28 lines, and is treated as a copy.

Memory and context Project management

context-age

Envejecimiento semántico del decision-log — comprime y archiva decisiones antiguas.

gonzalezpazmonica/pm-workspace · 22 tokens

handoff

Write a session handoff document for continuity.

travisjneuman/.claude · 8 tokens

lavra-checkpoint

Save session progress by filing beads, capturing knowledge, and syncing state.

roberto-mello/lavra · 18 tokens

capture-observation

Append one observation, question, hypothesis, or concern to TASKSTATE.md as lean, append-only task memory, leaving other artifacts and work undisturbed. Use when something surfaces mid-work, a hypothesis needs logging, or a concern is too small for decision-interview or targeted-questions. Do not use for a decision…

Mozurok/fhorja.dev · 105 tokens

finish-work

A project wrap-up command for the auto-embedded framework, which supports structured embedded-software development. It runs automated checks, guides a three-part review, records reusable lessons and session notes, and archives the finished task.

DunCanYounG-1/auto-embedded · 0 tokens

fio

Gerencia threads de contexto persistentes para trabalho entre sessões.

luanpdd/kit-mcp · 13 tokens

okite-ai: Command for Claude Code