quiz

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

A learning quiz helper based on the current coding session and, when available, a record of topics from earlier sessions. It asks recall questions and tracks which concepts need more practice.

In plain words
What is it for?
Use it to test understanding of decisions, code patterns, dependencies, fixes, or topics that the learning record marks as uncertain.
Why use it?
It turns passive reading of session history into active practice and avoids repeatedly reviewing concepts that are already understood.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

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

Good fit Use it to test understanding of decisions, code patterns, dependencies, fixes, or topics that the learning record marks as uncertain.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/gkaria/vibe-learn/quiz/github.svg)](https://agentmods.dev/skills/gkaria/vibe-learn/quiz)
Your own site
<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.

agentmods 80×15 button for quiz

Your own site · 80×15
<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>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 561 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.00561
Opus 5.5 $0.00012 $0.00224
Sonnet 5.5 $0.00006 $0.00112
Haiku 4.5 $0.00003 $0.00056

Measured 6d ago against content hash 654cc467152b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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

adapters/copilot-cli/skills/quiz/SKILL.md · 29 lines

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; 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 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, run knowledge.sh due and 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:

  1. Prefer "why" and "what would break" questions over trivia.
  2. Ask one question at a time; wait for the user's answer before revealing anything.
  3. 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.
  4. After the last question, record one knowledge.sh record <name> --label="..." --status=<solid|shaky> "--files=<path,path>" call per concept quizzed, with --notes on what was shaky and --files listing the project-relative files the question was grounded in, so the briefing links the concept to them. Use stable kebab-case names so the same concept is recognised across sessions.
  5. 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.

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. 6d ago Changed 654cc467152b
  2. 1mo ago Changed · +1 lines a19a473f76a5
  3. 1mo ago First seen · 28 lines · 30 tokens per session scan A eb8e4a276521

Subscribe to this mod's changes

quiz is a skill published in the GitHub repository gkaria/vibe-learn (57 stars, last pushed 5d ago), licensed MIT. It adds 30 tokens to every session and 561 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.

Related

Other skills, from other repositories

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

lovstudio/skills · 123 tokens

lov-subtitle-freedom

Create learner-friendly English subtitles with level-aware glosses and optional spoiler-safe subtitle sidecars.

lovstudio/skills · 25 tokens

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.

lovstudio/skills · 90 tokens

flow-guide

Methodology guide for the zero-hardware, simulation-only PCB + firmware seven-step workflow (does NOT drive execution). Use when the user asks about this workflow, asks why one of its steps works the way it does, or starts a no-hardware hardware project — in that last case route them to the step skills instead of…

raisoninme/boardless-pcb · 124 tokens

mdbook

This skill should be used when the user asks about "mdBook", "mdbook", "book.toml", "SUMMARY.md", "mdbook build", "mdbook serve", "mdbook init", "mdbook watch", "mdbook test", "mdbook clean", "mdBook configuration", "mdBook preprocessor", "mdBook renderer", "mdBook backend", "mdBook theme", "mdBook syntax…

marceloeatworld/mdbook-ai-skill · 180 tokens