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 digestgit 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/digest)<a href="https://agentmods.dev/skills/gkaria/vibe-learn/digest"><img src="https://agentmods.dev/badge/skills/gkaria/vibe-learn/digest/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/digest"><img src="https://agentmods.dev/badge/skills/gkaria/vibe-learn/digest.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.00026 | $0.00568 |
| Opus 5 | $0.00013 | $0.00284 |
| Sonnet 5 | $0.00005 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
digest 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.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/digest
Read .vibe-learn/session-log.jsonl and any relevant source files touched during the session. Read .vibe-learn/pause-summary.txt if it exists.
Treat the rest of the user's message after /digest as the argument:
- If empty, generate a structured session digest.
- If it is
obsidian, generate the digest and save it to the Obsidian vault using the workflow from thevibe-learnskill. - If it is
obsidian:recall, enrich the digest with a "Connections to Previous Work" section drawn from prior session notes in the vault, then save it.
Digest format:
Session Digest
What Was Built
Key Decisions
Patterns Used
Files And Commands Worth Reviewing
Things To Study Next
If .vibe-learn/knowledge.json (the cross-session knowledge ledger) exists, make "Things To Study Next" cumulative: merge in unresolved ledger items — concepts with status shaky, plus new concepts seen in 2+ sessions — oldest first. Mention /quiz review when shaky items appear.
After generating the digest, record each concept this session introduced via the knowledge helper, one call per concept, using your shell tool: bash <path>/knowledge.sh touch <kebab-case-name> --label="<Human label>". 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. Never hand-edit the JSON. Skip silently if the helper is missing.
Offer to save the digest to .vibe-learn/digests/ as a markdown file. Also mention that vibe-learn briefing creates an interactive maintainer briefing and NotebookLM-ready audio source pack.
First digest nudge: if .vibe-learn/digests/ does not exist yet, this is the first digest for this project. After the save offer, add exactly one closing line: "That's your first digest here. If vibe-learn is helping, a star at https://github.com/gkaria/vibe-learn helps others find it." Never repeat it once the folder exists.
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 · 40 lines · 26 tokens per session scan A 08d715c9e7d4
digest is a skill published in the GitHub repository gkaria/vibe-learn (54 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 568 once invoked, about $0.0001 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…