Borrowing it
Nothing to install: this file belongs to growilabs/growi-mcp-server. 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/growilabs/growi-mcp-server/main/.claude/commands/kiro/steering.mdgit clone --depth 1 https://github.com/growilabs/growi-mcp-serverWrote 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/growilabs/growi-mcp-server/steering)<a href="https://agentmods.dev/commands/growilabs/growi-mcp-server/steering"><img src="https://agentmods.dev/badge/commands/growilabs/growi-mcp-server/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.
<a href="https://agentmods.dev/commands/growilabs/growi-mcp-server/steering"><img src="https://agentmods.dev/badge/commands/growilabs/growi-mcp-server/steering.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.00012 | $0.00408 |
| Opus 5.5 | $0.00005 | $0.00163 |
| Sonnet 5.5 | $0.00002 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
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.
This is a copy
92% identical to steering — 16 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.
What it actually says
Kiro Steering Management
Mode Detection
Perform detection before invoking Subagent:
Check .kiro/steering/ status:
- Bootstrap Mode: Empty OR missing core files (product.md, tech.md, structure.md)
- Sync Mode: All core files exist
Use Glob to check for existing steering files.
Invoke Subagent
Delegate steering management to steering-agent:
Use the Task tool to invoke the Subagent with file path patterns:
Task(
subagent_type="steering-agent",
description="Manage steering files",
prompt="""
Mode: {bootstrap or sync based on detection}
File patterns to read:
- .kiro/steering/*.md (if sync mode)
- .kiro/settings/templates/steering/*.md
- .kiro/settings/rules/steering-principles.md
JIT Strategy: Fetch codebase files when needed, not upfront
"""
)
Display Result
Show Subagent summary to user:
Bootstrap:
- Generated steering files: product.md, tech.md, structure.md
- Review and approve as Source of Truth
Sync:
- Updated steering files
- Code drift warnings
- Recommendations for custom steering
Notes
- All
.kiro/steering/*.mdloaded as project memory - Templates and principles are external for customization
- Focus on patterns, not catalogs
- "Golden Rule": New code following patterns shouldn't require steering updates
- Avoid documenting agent-specific tooling directories (e.g.
.cursor/,.gemini/,.claude/) .kiro/settings/content should NOT be documented in steering files (settings are metadata, not project knowledge)- Light references to
.kiro/specs/and.kiro/steering/are acceptable; avoid other.kiro/directories
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 · 63 lines · 12 tokens per session scan A 7e1a8949ad60
steering is a command published in the GitHub repository growilabs/growi-mcp-server (20 stars, last pushed 16d ago), licensed MIT. It adds 12 tokens to every session and 408 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to steering, differing in 16 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.