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 youseiushida/benkyo --skill benkyo-session-wrapgit clone --depth 1 https://github.com/youseiushida/benkyoWrote 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/youseiushida/benkyo/benkyo-session-wrap)<a href="https://agentmods.dev/skills/youseiushida/benkyo/benkyo-session-wrap"><img src="https://agentmods.dev/badge/skills/youseiushida/benkyo/benkyo-session-wrap/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/youseiushida/benkyo/benkyo-session-wrap"><img src="https://agentmods.dev/badge/skills/youseiushida/benkyo/benkyo-session-wrap.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.00128 | $0.02762 |
| Opus 5 | $0.00064 | $0.01381 |
| Sonnet 5 | $0.00026 | $0.00552 |
| Haiku 4.5 | $0.00013 | $0.00276 |
Grade A, and why
benkyo-session-wrap 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 10d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
benkyo-session-wrap: ending a session cleanly
The end of a session is where most of the persistent state for future sessions gets captured. Without doing this carefully, the next session starts from confusion. With it done well, the learner picks up exactly where they left off.
Cardinal vocabulary rule
At wrap time the temptation is highest to "summarize technically". Resist. Recap accomplishments in natural language only.
Never say:
- 「treatment を 3 つ blackbox に設定しました」
- 「concept c5 を commit しました」
- 「session_end イベントを書きました」
- 「session note を project.metadata に追記しました」
- 「delayed JOL を仕込みます」
- 「event log に X を record した」
Forbidden internal terms (this is in addition to the standard cardinal vocabulary list):
event, log, record, schema, JSON, metadata, session_end, delayed_jol, hypercorrection, payload, kind (as in event kind)
Instead say:
- 「今日は留数定理をちゃんと理解する形にした」
- 「ラプラス変換は公式表で使う形に整理した」
- 「次回までに覚えてられそうなの教えて」(do NOT say "JOL")
Internal IDs are also forbidden: never write c1, p1, prj1 etc. in learner-facing wrap text — recaps are especially tempting to summarize technically. Refer to concepts and problems by their natural-language name.
See ../_benkyo-shared/references/nl-to-cli.md.
When this skill triggers
- Learner directly indicates session end ("終わり", "今日はここまで", "また明日", "疲れた", "時間ない")
- A topic has just completed and the session has been long; tutor proposes stopping
- An abrupt interruption ("急用が入った", "もう寝る")
- A drift past natural stopping points; tutor offers a wrap
This skill complements benkyo-tutoring. Tutoring is the in-session behavior; this is the boundary.
When this skill does NOT apply — defer to project-init
This skill handles session endings, not starts. If the learner is opening a session (especially after a gap), do NOT use the standard wrap protocol. Instead defer:
- 「久しぶり」「ようやく続き始めるかー」「何やってたっけ」 → defer to
benkyo-project-init("Returning after a long gap" handling) - 「再開」「続き」at the top of a session → defer to
benkyo-tutoringsession-start protocol
What ships with it
2 files 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.
- 10d ago First seen · 258 lines · 128 tokens per session scan A 9b8383bf81db
benkyo-session-wrap is a skill published in the GitHub repository youseiushida/benkyo (2 stars, last pushed 3mo ago), licensed MIT. It adds 128 tokens to every session and 2,762 once invoked, about $0.0006 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
get-rep-call-feedback
Use when the user wants evidence-backed coaching for one rep's calls, especially by comparing the rep with peer examples to identify repeatable best practices, specific upgrade moments, and practical next-call language.
tutorial
Interactive tutorial teaching Ouroboros hands-on.
model-router
A model-selection workflow that assigns different coding tasks to different AI models based on their abilities, cost, and the task’s risk or complexity.
rexai-image-generation
An image-generation skill that uses RexAI to create new images from text or transform existing images from other images. It returns the result as a local file.
verification-loop
Evidence-before-assertions workflow. Use before claiming work is done, before release, and after any behavior change in scripts/skills/MCP.
paper-explain-figures
A workflow for explaining figures from research papers, including what charts, diagrams, or images show and how to read them.