A session-learning helper that reads the project's activity log and explains what happened during a coding session. It can answer questions, save learning notes to Obsidian, and use a knowledge record when available.

Use it to review a session, understand why code changed, identify files and patterns worth studying, or save and recall learning notes.

It removes the need to reconstruct changes, decisions, and commands from scattered files and terminal history. It gives context for understanding work that has already been done.

learn — Skill for Claude Code by gkaria/vibe-learn

Install

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.

Any agent

npx skills add gkaria/vibe-learn --skill learn

Clone the repo

git clone --depth 1 https://github.com/gkaria/vibe-learn

Made for: Claude Code.

Or install vibe-learn, the plugin that ships this one along with the rest of its 5 skills, 4 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gkaria/vibe-learn/learn/github.svg)](https://agentmods.dev/skills/gkaria/vibe-learn/learn)

Your own site

<a href="https://agentmods.dev/skills/gkaria/vibe-learn/learn"><img src="https://agentmods.dev/badge/skills/gkaria/vibe-learn/learn/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gkaria/vibe-learn/learn"><img src="https://agentmods.dev/badge/skills/gkaria/vibe-learn/learn.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 613 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00030	$0.00613
Opus 5.5	$0.00012	$0.00245
Sonnet 5.5	$0.00006	$0.00123
Haiku 4.5	$0.00003	$0.00061

Measured 6d ago against content hash b4db79b0582a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

learn 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.

adapters/copilot-cli/skills/learn/SKILL.md · 25 lines

What it actually says

/learn

Read .vibe-learn/session-log.jsonl to understand what happened in this session. Read .vibe-learn/pause-summary.txt if it exists

Briefing (all modes): before anything else, refresh the session briefing: run vibe-learn briefing --if-stale via your shell tool. If vibe-learn is not on PATH, run bash <dir>/briefing.sh --if-stale, where <dir> is the directory that holds vibe-learn's knowledge.sh (scripts/ in a full install, the hooks directory in a techpack install) (found with the knowledge-helper lookup; ~/.vibe-learn/scripts/ for a global install). It returns at once when the briefing is current. Skip it silently if neither exists, and do not mention its output unless it fails.

Treat the rest of the user's message after /learn as the argument:

If empty, explain the most recent session activity in plain language: what changed, why the assistant likely made those choices, which files, commands, or patterns matter, and what to study next.
If it starts with obsidian, follow the Obsidian save and recall workflow from the vibe-learn skill (obsidian saves a learn note; obsidian:recall <topic> searches the vault and writes nothing).
Otherwise, answer it as a specific question grounded in the session log and the relevant changed files.

Knowledge helper: if .vibe-learn/knowledge.json exists, run the helper's due command via your shell tool. Locate knowledge.sh in this order: ~/.vibe-learn/scripts/knowledge.sh; read .github/hooks/vibe-learn.json (then ${COPILOT_HOME:-$HOME/.copilot}/hooks/vibe-learn.json) and extract the first non-empty .hooks[][] | .env.VIBE_LEARN_INSTALL_DIR value, then append /scripts/knowledge.sh; scripts/knowledge.sh when working in the vibe-learn repo itself. If a due concept was also touched in this session, open with a single heads-up line pointing to /quiz review — never let it block the actual answer. Skip silently if the ledger or helper is missing.

Mention once that vibe-learn briefing generates an interactive maintainer briefing and NotebookLM-ready audio source pack, and that vibe-learn recap produces a shareable weekly rollup.

If the session log is missing or empty, say vibe-learn has not captured events for this project yet (repository hooks in .github/hooks/ load when Copilot CLI opens the project) and offer to help from available repository context.

Changes

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 Changed · +2 lines b4db79b0582a
1mo ago Changed · +1 lines 4f9ce1cd5dff
1mo ago First seen · 22 lines · 30 tokens per session scan A 14f6c7ef3d03

Subscribe to this mod's changes

learn is a skill published in the GitHub repository gkaria/vibe-learn (57 stars, last pushed 5d ago), licensed MIT. It adds 30 tokens to every session and 613 once invoked, about $0.0001 per session on Opus 5.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-09-07.

Claude Code Learning and teaching Writing and docs ai-coding-assistant claude-code-plugin codex cursor developer-tools

lov-hanzi-lens

A research and infographic workflow for explaining one Chinese character, including its pronunciation, written form, history, meanings, and use in classical texts.

lovstudio/skills · 82 tokens

lov-algo-viz-creator

A generator for self-contained HTML demonstrations that show an algorithm, data structure, or information flow one step at a time. Each step can include an explanation and highlighted pseudocode, with controls for playback, pausing, stepping, speed, and keyboard use.

lovstudio/skills · 123 tokens

lov-subtitle-freedom

Create learner-friendly English subtitles with level-aware glosses and optional spoiler-safe subtitle sidecars.

lovstudio/skills · 25 tokens

lov-thesis-polish

An academic editing tool for improving an MBA thesis or dissertation in Markdown, a plain-text format for structured documents. It addresses language, argument structure, logic, research contributions, and formatting.

lovstudio/skills · 90 tokens

flow-guide

Methodology guide for the zero-hardware, simulation-only PCB + firmware seven-step workflow (does NOT drive execution). Use when the user asks about this workflow, asks why one of its steps works the way it does, or starts a no-hardware hardware project — in that last case route them to the step skills instead of…

raisoninme/boardless-pcb · 124 tokens

mdbook

This skill should be used when the user asks about "mdBook", "mdbook", "book.toml", "SUMMARY.md", "mdbook build", "mdbook serve", "mdbook init", "mdbook watch", "mdbook test", "mdbook clean", "mdBook configuration", "mdBook preprocessor", "mdBook renderer", "mdBook backend", "mdBook theme", "mdBook syntax…

marceloeatworld/mdbook-ai-skill · 180 tokens