Borrowing it
Nothing to install: this file belongs to akaghef/M3E. 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/akaghef/M3E/main/.agents/skills/kiro-steering/SKILL.mdgit clone --depth 1 https://github.com/akaghef/M3EWrote 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/skills/akaghef/m3e/kiro-steering)<a href="https://agentmods.dev/skills/akaghef/m3e/kiro-steering"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/kiro-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/skills/akaghef/m3e/kiro-steering"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/kiro-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.00017 | $0.01049 |
| Opus 5.5 | $0.00007 | $0.00420 |
| Sonnet 5.5 | $0.00003 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
kiro-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 157 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):
Parallel Research
The following research areas are independent and can be executed in parallel:
- Product analysis: README, package.json, documentation files for purpose, value, core capabilities
- Tech analysis: Config files, dependencies, frameworks for technology patterns and decisions
- Structure analysis: Directory tree, naming conventions, import patterns for organization
If multi-agent is enabled, spawn sub-agents for each area above. Otherwise execute sequentially.
After all parallel research completes, synthesize patterns for steering files.
- 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
rules/steering-principles.mdfrom this skill's directory - 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
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 157 lines · 17 tokens per session scan A 0ed80e5e6441
kiro-steering is a skill published in the GitHub repository akaghef/M3E (11 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 1,049 once invoked, about $0.0001 per session on Opus 5.5. 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-10-02.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…