learn

learn is a skill for Claude Code from gkaria/vibe-learn. It costs 30 tokens per session (467 once invoked), scanned A, original, MIT.

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.

In plain words
What is it for?
Use it to review a session, understand why code changed, identify files and patterns worth studying, or save and recall learning notes.
Why use it?
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.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Part of the vibe-learn plugin — 5 skills, 4 commands shipped together

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

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gkaria/vibe-learn/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.

agentmods badge for learn

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.

agentmods 80×15 button for learn

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

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.00467
Opus 5 $0.00015 $0.00234
Sonnet 5 $0.00006 $0.00093
Haiku 4.5 $0.00003 $0.00047

Measured yesterday against content hash 14f6c7ef3d03, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 yesterday.

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/cursor/skills/learn/SKILL.md · 22 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 — Cursor does not inject pause summaries into context, so this file is the only place the last turn's summary lives.

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; the scripts/knowledge.sh under the VIBE_LEARN_DIR baked into .cursor/hooks/vibe-learn.sh or ~/.cursor/hooks/vibe-learn.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 (project hooks in .cursor/hooks.json only run in a trusted workspace) 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.

  1. yesterday 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 (54 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 467 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-09-07.

Related

Other skills, from other repositories

pneuma-bansho

A board-based way to explain ideas through written Markdown, a simple text-formatting language, with the writing appearing progressively like a live lecture.

pandazki/pneuma-skills · 0 tokens

xray

Investigate how a concept, code path, application, network flow, system, incident, document, or local artifact actually works, then deliver a two-depth visual HTML explainer with a dead-simple big-picture first layer and source-backed technical depth behind it. Use when the user invokes $xray, asks how something works…

majiayu000/spellbook · 131 tokens

procoder

Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…

azrtydxb/procoder · 101 tokens

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-gh-access

Open a private GitHub repo to external clients or contractors without making it public. Accepts a mixed list of GitHub usernames and/or email addresses, resolves each to a GitHub account (falling back to an email invitation when the user has no discoverable account yet), and invites them as collaborators with a chosen…

lovstudio/skills · 151 tokens

lov-gh-tidy

Interactive GitHub repo hygiene skill. Lists all open issues, PRs, stale branches, and orphan labels, shows a summary of each with analysis, then asks the user how to handle each item (close, merge, comment, delete, keep). Executes all chosen actions via gh CLI. Use when the user says "清理 GitHub", "tidy repo", "clean…

lovstudio/skills · 95 tokens