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/cocorof/geny/summarize_sessionnpx skills add CocoRoF/Geny --skill summarize_sessiongit clone --depth 1 https://github.com/CocoRoF/GenyWrote 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/cocorof/geny/summarize_session)<a href="https://agentmods.dev/skills/cocorof/geny/summarize_session"><img src="https://agentmods.dev/badge/skills/cocorof/geny/summarize_session.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 | $0.00032 | $0.00266 |
| Opus 5 | $0.00016 | $0.00133 |
| Sonnet 5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
summarize-session 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 4d 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.
What it actually says
Summarize Session
You are summarising the current Geny session for the operator. Produce a tight three-paragraph summary:
1. Topics covered (bullet sentences). What was the operator working on? List 3–6 concrete topics with one-sentence descriptions each.
2. Decisions and conclusions. What was decided, agreed on, or accepted? Distinguish "decided" (won't re-litigate) from "leaning toward" (still open).
3. Open follow-ups. What's unfinished? What needs the operator's input? What would the next session start with?
Use memory_search / memory_list / memory_read to ground the summary in the session's actual notes — do NOT make up content. If the memory backend is empty, say so explicitly instead of fabricating.
Keep the summary under ~250 words. Use plain prose, not lists for the body of each paragraph.
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.
- 4d ago First seen · 28 lines · 32 tokens per session scan A f809615714a6
summarize-session is a skill published in the GitHub repository CocoRoF/Geny (10 stars, last pushed 5d ago), licensed Apache-2.0. It adds 32 tokens to every session and 266 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
hive.context-preservation
Proactively extract critical values from tool results into working notes before automatic context pruning destroys them.
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.
enhance-claude-memory
Use when improving CLAUDE.md or AGENTS.md project memory files.
learn
Research any topic online and create learning guides. Use when user asks to 'learn about', 'research topic', 'create learning guide', 'build knowledge base', or 'study subject'.
perf-profiler
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.
memclaw
The agent's persistent long-term memory — the only knowledge that survives across sessions, shared across the fleet under access control. Consult it at the start of a task to recall prior decisions, findings, and rules before acting, and write outcomes, decisions, and lessons as work completes. Use whenever a caura…