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.
curl -O https://raw.githubusercontent.com/j5ik2o/okite-ai/main/.claude/commands/kiro/steering-custom.mdgit clone --depth 1 https://github.com/j5ik2o/okite-aiWrote 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/okite-ai/steering-custom)<a href="https://agentmods.dev/commands/j5ik2o/okite-ai/steering-custom"><img src="https://agentmods.dev/badge/commands/j5ik2o/okite-ai/steering-custom/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.
<a href="https://agentmods.dev/commands/j5ik2o/okite-ai/steering-custom"><img src="https://agentmods.dev/badge/commands/j5ik2o/okite-ai/steering-custom.svg" alt="Reviewed on agentmods" width="80" 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.00008 | $0.00944 |
| Opus 5 | $0.00004 | $0.00472 |
| Sonnet 5 | $0.00002 | $0.00189 |
| Haiku 4.5 | $0.00001 | $0.00094 |
Grade A, and why
steering-custom 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 7d 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
91% identical to kiro-steering-custom — 23 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kiro Custom Steering Creation
<background_information> Role: Create specialized steering documents beyond core files (product, tech, structure).
Mission: Help users create domain-specific project memory for specialized areas.
Success Criteria:
- Custom steering captures specialized patterns
- Follows same granularity principles as core steering
- Provides clear value for specific domain </background_information>
-
Ask user for custom steering needs:
- Domain/topic (e.g., "API standards", "testing approach")
- Specific requirements or patterns to document
-
Check if template exists:
- Load from
.kiro/settings/templates/steering-custom/{name}.mdif available - Use as starting point, customize based on project
- Load from
-
Analyze codebase (JIT) for relevant patterns:
- Glob for related files
- Read for existing implementations
- Grep for specific patterns
-
Generate custom steering:
- Follow template structure if available
- Apply principles from
.kiro/settings/rules/steering-principles.md - Focus on patterns, not exhaustive lists
- Keep to 100-200 lines (2-3 minute read)
-
Create file in
.kiro/steering/{name}.md
Available Templates
Templates available in .kiro/settings/templates/steering-custom/:
- api-standards.md - REST/GraphQL conventions, error handling
- testing.md - Test organization, mocking, coverage
- security.md - Auth patterns, input validation, secrets
- database.md - Schema design, migrations, query patterns
- error-handling.md - Error types, logging, retry strategies
- authentication.md - Auth flows, permissions, session management
- deployment.md - CI/CD, environments, rollback procedures
Load template when needed, customize for project.
Steering Principles
From .kiro/settings/rules/steering-principles.md:
- Patterns over lists: Document patterns, not every file/component
- Single domain: One topic per file
- Concrete examples: Show patterns with code
- Maintainable size: 100-200 lines typical
- Security first: Never include secrets or sensitive data
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.
- 7d ago First seen · 128 lines · 8 tokens per session scan A ab7457cd911b
steering-custom is a command published in the GitHub repository j5ik2o/okite-ai (81 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 944 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to kiro-steering-custom, differing in 23 lines, and is treated as a copy.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.