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 gkaria/vibe-learn --skill learngit clone --depth 1 https://github.com/gkaria/vibe-learnWrote 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/gkaria/vibe-learn/learn)<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.
<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>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.00467 |
| Opus 5 | $0.00015 | $0.00234 |
| Sonnet 5 | $0.00006 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
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.
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 thevibe-learnskill (obsidiansaves 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.
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.
- yesterday First seen · 22 lines · 30 tokens per session scan A 14f6c7ef3d03
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.
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.
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…
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…
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.
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…
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…