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 explaingit 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/explain)<a href="https://agentmods.dev/skills/gkaria/vibe-learn/explain"><img src="https://agentmods.dev/badge/skills/gkaria/vibe-learn/explain/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/explain"><img src="https://agentmods.dev/badge/skills/gkaria/vibe-learn/explain.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.00033 | $0.00909 |
| Opus 5.5 | $0.00013 | $0.00364 |
| Sonnet 5.5 | $0.00007 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
explain 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/explain
Read .vibe-learn/session-log.jsonl to see what this session touched and why (the user_prompt events carry the intent). Read .vibe-learn/knowledge.json if it exists (the cross-session knowledge ledger).
Knowledge helper: to mark concepts as seen, use the knowledge.sh helper via your shell tool — never hand-edit the JSON. Locate it 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 none of these exist, skip the ledger step silently — the tour itself still works.
Treat the rest of the user's message after /explain as the target:
Target: none
If nothing follows /explain: tour the most significant file or subsystem this session touched. Prefer, in order: a newly created file that other touched files import; the file edited most often; the file behind the goal stated in the last user_prompt. Say which one you picked and why in one line.
Target: <file>
If the argument names a path that exists: tour that file.
Target: <topic>
Otherwise treat the argument as a topic (e.g. auth flow, the retry logic): find the files behind it — start from the session log, then grep the codebase — and tour them as one subsystem. If nothing matches, say so and list what the session did touch.
Tour structure (all targets)
Read the target file(s) and their immediate callers and callees before writing anything. Walk the code top-down as a colleague would at a whiteboard:
- Entry point — where execution starts and what triggers it (a request, a hook event, a CLI call, an import).
- The spine — the 3–5 load-bearing pieces, in execution order. For each, say why it is there, not just what it does. Quote the real line with a
path:linereference. - The edges — error paths, ordering constraints, defaults, and anything that would break if rearranged or removed.
- Connections — what calls this, what this calls, and where a change here would ripple.
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 9b69493aaa27
- 1mo ago Changed · +1 lines 6445cccff00b
- 1mo ago First seen · 50 lines · 33 tokens per session scan A 69714562f9b3
explain is a skill published in the GitHub repository gkaria/vibe-learn (57 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 909 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.
Other skills, from other repositories
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-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.
lov-subtitle-freedom
Create learner-friendly English subtitles with level-aware glosses and optional spoiler-safe subtitle sidecars.
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.
lov-code-review
A code review assistant that examines a real code change for defects, security problems, and maintenance risks. A code review is a check of proposed changes before they are accepted.