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 iamcxa/kc-claude-plugins --skill kc-session-resumegit clone --depth 1 https://github.com/iamcxa/kc-claude-pluginsWrote 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/iamcxa/kc-claude-plugins/kc-session-resume)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/kc-session-resume"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/kc-session-resume/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/iamcxa/kc-claude-plugins/kc-session-resume"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/kc-session-resume.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.00047 | $0.02275 |
| Opus 5 | $0.00023 | $0.01137 |
| Sonnet 5 | $0.00009 | $0.00455 |
| Haiku 4.5 | $0.00005 | $0.00228 |
Grade A, and why
kc-session-resume 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 9d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Resume
Restore context from a previous session's journal handoff entry.
Companion skill: kc-session-handoff creates the entries this skill reads.
Routing
Priority order — explicit handoff ID always wins:
- User gave handoff ID (
YYYY-MM-DD/HH-MM-SS-nnnnnnnpattern) → Go directly to step 2A. Do NOT check GSD checkpoints, do NOT read .continue-here.md, do NOT read STATE.md. The handoff ID is the sole intent signal — GSD state is irrelevant when the user points to a specific journal entry. - No handoff ID → Check GSD structure:
ls .planning/phases/*/.continue-here.md 2>/dev/null ls .planning/STATE.md 2>/dev/null- GSD checkpoint found → Check for recent journal handoffs too (step 2B preview:
list_recent_entries(days: 3, limit: 3, type: "project")). If BOTH GSD checkpoint AND journal handoffs exist → you MUST present numbered options and wait for user choice:
User picks GSD → invoke找到兩種可恢復的上下文: 1. GSD Phase {N}: {description} (checkpoint) 2. Journal handoff: {branch} — {description} ({date}) 要恢復哪一個?/gsd:resume-work. User picks journal → continue to step 2B. Do NOT merge both sources on your own judgment. Do NOT auto-select "the most recent one." Even if they point to the same branch, they represent different resume mechanisms — the user decides which context to restore. - GSD checkpoint only (no recent journal handoffs) → Inform user, invoke
/gsd:resume-work. - No GSD → Continue to step 1.
- GSD checkpoint found → Check for recent journal handoffs too (step 2B preview:
Process
1. Extract Clues (no handoff ID path only)
Extract branch name / topic keywords from prompt. Fallback: git branch --show-current.
Also check current state:
git branch --show-current
git status --short
git log --oneline -3
git rev-parse --show-toplevel
Derive repo slug (same logic as kc-session-handoff Step 1.5):
REPO_SLUG=$(basename "$(git rev-parse --path-format=absolute --git-common-dir 2>/dev/null | sed 's|/\.git$||')" 2>/dev/null | tr '[:upper:]' '[:lower:]')
REPO_SLUG=${REPO_SLUG:-$(basename "$(pwd)" | tr '[:upper:]' '[:lower:]')}
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.
- 9d ago First seen · 249 lines · 47 tokens per session scan A fe4110d38e14
kc-session-resume is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,275 once invoked, about $0.0002 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.