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-session-managementgit 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-session-management)<a href="https://agentmods.dev/skills/navendubrajesh/context-management-for-agents/kiro-session-management"><img src="https://agentmods.dev/badge/skills/navendubrajesh/context-management-for-agents/kiro-session-management/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-session-management"><img src="https://agentmods.dev/badge/skills/navendubrajesh/context-management-for-agents/kiro-session-management.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.00086 | $0.00916 |
| Opus 5 | $0.00043 | $0.00458 |
| Sonnet 5 | $0.00017 | $0.00183 |
| Haiku 4.5 | $0.00009 | $0.00092 |
Grade A, and why
kiro-session-management 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 12d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kiro Session Management
Kiro does not expose a Copilot-style /compact command. Instead, spec artifacts and steering files are the durable session layer — chat is ephemeral orchestration atop persisted markdown. This skill covers keeping long spec-driven work coherent without relying on verbatim chat history.
When to Activate
Activate this skill when:
- Kiro's implementation diverges from an earlier requirements or design document
- A multi-phase feature spans multiple chat sessions over days
- Deciding whether to update specs, regenerate tasks, or start a fresh Kiro chat
- Chat suggestions conflict with always-on steering or foundational docs
- A spec task list becomes stale mid-implementation
Do not activate this skill for adjacent work owned by other skills:
- Do not activate for steering file authoring and inclusion modes:
kiro-customization. - Do not activate for how steering and specs enter context:
kiro-context-architecture. - Do not activate for Copilot-style CLI compaction:
copilot-session-management. - Do not activate for platform-agnostic summarization algorithms:
context-compression.
Core Concepts
Specs as external memory
The spec workflow produces requirements.md, design.md, and tasks.md (or equivalent). These files survive chat resets and should be treated as the source of truth. When chat and spec disagree, update the spec first, then ask Kiro to realign — not the reverse.
Chat is orchestration, not storage
Kiro chat drives execution against specs but does not reliably preserve fine-grained decisions across long threads. Move durable decisions into steering or spec files immediately — especially acceptance criteria, API contracts, and task boundaries.
When to refresh specs vs continue chat
Refresh specs when: scope changed materially, tasks completed invalidate downstream items, or design assumptions proved wrong.
Continue chat when: iterating on a single task with clear acceptance criteria and steering still accurate.
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.
- 12d ago First seen · 76 lines · 86 tokens per session scan A 57037397991c
kiro-session-management is a skill published in the GitHub repository navendubrajesh/context-management-for-agents (2 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 916 once invoked, about $0.0004 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
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 and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.