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 quizgit 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/quiz)<a href="https://agentmods.dev/skills/gkaria/vibe-learn/quiz"><img src="https://agentmods.dev/badge/skills/gkaria/vibe-learn/quiz/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/quiz"><img src="https://agentmods.dev/badge/skills/gkaria/vibe-learn/quiz.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.00508 |
| Opus 5 | $0.00015 | $0.00254 |
| Sonnet 5 | $0.00006 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
quiz 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
/quiz
Read .vibe-learn/session-log.jsonl to understand what happened in this session. Read .vibe-learn/knowledge.json if it exists (the cross-session knowledge ledger).
Knowledge helper: to read or update the ledger, use the knowledge.sh helper via your shell tool — never hand-edit the JSON. Locate it 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 the helper is missing, skip ledger updates and say so briefly.
Treat the rest of the user's message after /quiz as the argument:
- If empty, quiz on this session: select 3–5 quizzable moments from the session log — decisions, patterns, dependencies added, failures that were fixed.
- If it is
review, runknowledge.sh dueand quiz on concepts that are shaky or haven't been quizzed recently. If nothing is due, say so and offer a session quiz instead. - Otherwise, treat it as a topic and quiz on it, drawing from the session log, the ledger, and relevant source files.
Question flow:
- Prefer "why" and "what would break" questions over trivia.
- Ask one question at a time; wait for the user's answer before revealing anything.
- After each answer, say what the user got right, what they missed, and give a 1–2 sentence correct explanation. Colleague tone, never an exam.
- After the last question, record one
knowledge.sh record <name> --label="..." --status=<solid|shaky>call per concept quizzed, with--noteson what was shaky. Use stable kebab-case names so the same concept is recognised across sessions. - Close with a short recap and, if anything was shaky, point to
/learn <topic>or/explain <file>.
If the session log is empty and no ledger exists, say vibe-learn has nothing to quiz on yet and stop.
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 · 28 lines · 30 tokens per session scan A eb8e4a276521
quiz 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 508 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…