Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add navendubrajesh/context-management-for-agents --skill kiro-customizationgit clone --depth 1 https://github.com/navendubrajesh/context-management-for-agentsWrote 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/navendubrajesh/context-management-for-agents/kiro-customization)<a href="https://agentmods.dev/skills/navendubrajesh/context-management-for-agents/kiro-customization"><img src="https://agentmods.dev/badge/skills/navendubrajesh/context-management-for-agents/kiro-customization/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/navendubrajesh/context-management-for-agents/kiro-customization"><img src="https://agentmods.dev/badge/skills/navendubrajesh/context-management-for-agents/kiro-customization.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.00102 | $0.01033 |
| Opus 5 | $0.00051 | $0.00517 |
| Sonnet 5 | $0.00020 | $0.00207 |
| Haiku 4.5 | $0.00010 | $0.00103 |
Grade A, and why
kiro-customization 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 11d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kiro Customization
Kiro's steering surface is markdown files with YAML frontmatter controlling when context loads. Combined with optional AGENTS.md, hooks, and MCP, this is the full user-controlled steering stack. This skill covers authoring steering well: inclusion modes, scoping, token budgeting, and failure modes.
When to Activate
Activate this skill when:
- Creating or restructuring
.kiro/steering/or global~/.kiro/steering/files - Choosing between
inclusion: always,fileMatch,manual, andautomodes - Generating or maintaining foundational steering (product, tech, structure)
- Kiro ignores conventions or applies global rules where workspace rules should win
- Configuring hooks or MCP servers for a Kiro workspace
Do not activate this skill for adjacent work owned by other skills:
- Do not activate for spec artifact lifecycle across sessions:
kiro-session-management. - Do not activate for how steering composes with specs in context:
kiro-context-architecture. - Do not activate for platform-agnostic instruction design:
context-fundamentals. - Do not activate for MCP tool schema authoring:
tool-design.
Core Concepts
Workspace vs global scope
.kiro/steering/— project-specific; wins on conflict~/.kiro/steering/— personal/team defaults for all workspaces- Team steering can be deployed via MDM to
~/.kiro/steering/
Put universal personal preferences globally; put repo-specific patterns in workspace steering.
Inclusion mode selection
| Need | Mode | Rationale |
|---|---|---|
| Stack, security, naming everywhere | always |
Baseline — keep lean |
| Component/API/test standards | fileMatch |
Loads only on relevant files |
| Rare runbooks, migrations | manual |
#name or / slash on demand |
| Heavy domain guides | auto |
Description-triggered like skills |
Foundational steering
Use Kiro's Generate Steering Docs for product.md, tech.md, structure.md. Treat these as always-on — audit quarterly; stale tech.md sends Kiro toward deprecated libraries.
What ships with it
1 file 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.
- 11d ago First seen · 87 lines · 102 tokens per session scan A 43fca5d8ea66
kiro-customization is a skill published in the GitHub repository navendubrajesh/context-management-for-agents (2 stars, last pushed 2mo ago), licensed MIT. It adds 102 tokens to every session and 1,033 once invoked, about $0.0005 per session on Opus 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…