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 agentmods add skills/nth5693/gemini-kit/session-resumenpx skills add nth5693/gemini-kit --skill session-resumegit clone --depth 1 https://github.com/nth5693/gemini-kitWrote 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/nth5693/gemini-kit/session-resume)<a href="https://agentmods.dev/skills/nth5693/gemini-kit/session-resume"><img src="https://agentmods.dev/badge/skills/nth5693/gemini-kit/session-resume.svg" alt="Measured on agentmods" 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.00009 | $0.00428 |
| Opus 5 | $0.00005 | $0.00214 |
| Sonnet 5 | $0.00002 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
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 6d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- session-resume — 100% identical, 0 lines differ
- session-resume — 100% identical, 0 lines differ
What it actually says
Session Resume Skill
Helps agents quickly understand where work left off when starting a new session.
When To Use
- At the start of any new conversation
- When context seems missing
- When user asks "what were we working on?"
Instrumentation
# Log usage when using this skill
./scripts/log-skill.sh "session-resume" "manual" "$$"
Quick Resume Checklist
1. Check Active Work
# Ready todos (highest priority)
ls todos/*-ready-*.md 2>/dev/null | head -5
# In-progress plans
ls plans/*.md 2>/dev/null
# Recent solutions (for context)
ls -t docs/solutions/**/*.md 2>/dev/null | head -3
2. Check Recent Git Activity
# Recent commits
git log --oneline -5
# Uncommitted changes
git status --short
3. Summarize Context
After gathering info, summarize:
4. Check System Health
./scripts/compound-dashboard.sh
Review health grade and recommendations before starting work.
5. Final Summary
📍 Session Context:
**Active Work:**
- {X} ready todos waiting
- Plan in progress: {plan name if any}
**Recent Activity:**
- Last commit: {subject}
- {Changed files if uncommitted}
**Suggested Next Steps:**
1. {Most logical next action}
2. {Alternative}
Automatic Triggers
Consider running this skill when you see:
- User starts with "continue", "resume", "where were we"
- First message in a new session
- User seems to lack context
References
- Todos:
todos/ - Plans:
plans/ - Solutions:
docs/solutions/ - Workflows:
.agent/workflows/
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.
- 6d ago First seen · 97 lines · 9 tokens per session scan A 3c2f9523ba4b
session-resume is a skill published in the GitHub repository nth5693/gemini-kit (375 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 428 once invoked, about $0.0000 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-30.
Other skills, from other repositories
qmd
Search the vault using QMD semantic search. Use PROACTIVELY before reading files. Preference order: (1) MCP tools — mcpqmdquery, mcpqmdget, mcpqmdmultiget, mcpqmdstatus — if they appear in your tool menu, use them first; (2) CLI qmd --index ... as fallback; (3) Grep/Glob only when QMD is not installed. Trigger…
neo4j-agent-memory-skill
Authoritative reference for the neo4j-agent-memory Python package — a graph-native memory system for AI agents built on Neo4j — and for the hosted service (NAMS) at memory.neo4jlabs.com. Use this skill whenever the user mentions neo4j-agent-memory, agent memory with Neo4j, context graphs, the POLE+O model…
context-degradation
Recognize patterns of context failure: lost-in-middle, poisoning, distraction, and clash.
lov-search-chat
从本机 Ataru 记忆索引里召回过去的 AI 会话上下文,返回可定位的命中与原文片段。 Use when asked what was discussed, decided, or fixed in an earlier session.
context-optimization
Apply compaction, masking, and caching strategies.
sageox
Complete toolkit for SageOx team knowledge. Query team context, manage AI coworkers, distill and summarize activity, see what coworkers are working on, catch up after time away, import/export knowledge, and manage configured repos. Use when: searching team discussions, loading expert agents, running distillation…