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 agentmods add instructions/gkaria/vibe-learn/claude-mdgit 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/instructions/gkaria/vibe-learn/claude-md)<a href="https://agentmods.dev/instructions/gkaria/vibe-learn/claude-md"><img src="https://agentmods.dev/badge/instructions/gkaria/vibe-learn/claude-md.svg" alt="Measured on agentmods" 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.04537 | $0.04537 |
| Opus 5 | $0.02269 | $0.02269 |
| Sonnet 5 | $0.00907 | $0.00907 |
| Haiku 4.5 | $0.00454 | $0.00454 |
Grade B, and why
vibe-learn CLAUDE.md scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
install.sh ← hook registration into ~/.claude/settings.json How it starts
The opening of the file, as written. The whole thing — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What This Project Is
vibe-learn is a coding assistant plugin that observes what the AI does during a development session and helps users understand what was built. It works by registering lifecycle hooks that capture tool use events (file writes, edits, bash commands) into an append-only JSONL session log, then surfaces summaries at natural pause points.
Product principle: users can outsource thinking to an assistant, but they cannot outsource understanding. The project should make AI-assisted work easier to learn from, not just easier to accept.
It supports Claude Code, Codex App/CLI, OpenCode, and Grok Build, with a generic adapter system for adding new assistants.
It requires no external API calls. Hooks are mechanical (bash + jq). The learning commands/prompts (/learn, /digest, /quiz, and the Codex/Grok vibe-learn skill) leverage the AI's own context window to generate explanations and reports.
Multi-Assistant Architecture
The project is split into a generic core and per-assistant adapters:
scripts/ ← assistant-agnostic core (accepts Claude and Grok hook envelopes)
bootstrap.sh ← SessionStart hook
capture-prompt.sh ← UserPromptSubmit hook
observe.sh ← PostToolUse hook (<50ms, append-only)
pause-summary.sh ← Stop hook
setup.sh ← global installer
install.sh ← per-project installer
cli.sh ← command dispatcher for install/dashboard
dashboard.sh ← static session briefing generator
knowledge.sh ← knowledge ledger helper (record/touch/list/due)
adapters/
claude-code/ ← Claude Code adapter
hooks.json ← hook registration template
commands/ ← /learn, /digest, and /quiz slash command files
install.sh ← hook registration into ~/.claude/settings.json
codex/ ← Codex App/CLI adapter
hooks.toml ← hook registration template (TOML)
prompts/ ← learn, digest, and quiz prompt-file fallbacks
skills/ ← global Codex vibe-learn skill
install.sh ← hook registration into ~/.codex/config.toml
opencode/ ← OpenCode adapter
plugins/ ← local plugin for event capture
commands/ ← /learn, /digest, and /quiz markdown commands
install.sh ← plugin/command install into .opencode or ~/.config/opencode
grok/ ← Grok Build adapter
hooks.json ← hook registration template
commands/ ← /learn, /digest, and /quiz slash command files
skills/ ← /vibe-learn skill
install.sh ← hook file + skill/command install into ~/.grok or .grok
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.
- 5d ago First seen · 256 lines · 4,537 tokens per session scan B 44283bda06c7
vibe-learn CLAUDE.md is an instructions file published in the GitHub repository gkaria/vibe-learn (54 stars, last pushed 9d ago), licensed MIT. It adds 4,537 tokens to every session, about $0.0227 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).