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 commands/gkaria/vibe-learn/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/commands/gkaria/vibe-learn/digest)<a href="https://agentmods.dev/commands/gkaria/vibe-learn/digest"><img src="https://agentmods.dev/badge/commands/gkaria/vibe-learn/digest.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 | $0.00024 | $0.01445 |
| Opus 5 | $0.00012 | $0.00723 |
| Sonnet 5 | $0.00005 | $0.00289 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade B, and why
digest 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 4d 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.
**Ledger update (all modes):** after generating the digest, record each concept this session introduced via the knowledge helper, one call per concept: `bash ~/.vibe-learn/scripts/knowledge.sh touch <kebab-case-name> --l How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read .vibe-learn/session-log.jsonl (the full log). Read any relevant source files to understand what was built.
Parse $ARGUMENTS to determine the mode:
Mode: obsidian:recall
If $ARGUMENTS is obsidian:recall:
Step 1 — Load config:
Check .vibe-learn/obsidian.json first, then ~/.vibe-learn/obsidian.json. If neither exists, run the same config setup flow as /digest obsidian (ask vault path, subfolder, global vs project save location) before proceeding.
Step 2 — Search for previous sessions on this project:
- Determine the project name from the working directory (last path component).
- Search
<vault_path>/<subfolder>/for markdown files where:- The frontmatter
projectfield matches the project name, OR - The filename contains the project name
- The frontmatter
- Read the most recent matching files (up to 5), ordered by
datefrontmatter descending.
Step 3 — Generate the enriched digest:
Produce the full structured digest as normal (What Was Built, Key Decisions, Patterns Used, Things to Study, Session Activity), then append a "Connections to Previous Work" section:
## Connections to Previous Work
- How this session builds on or continues prior work
- Recurring patterns seen across sessions
- Unchecked "Things to Study" items from past sessions relevant to what was just built
- Progression of understanding (e.g., "You first set up JWT auth on March 2nd, this session extends it with refresh tokens")
If no previous session notes are found for this project, note that in the section and omit the connections content.
Step 4 — Write the enriched note to the vault (same write behavior as /digest obsidian below).
Mode: obsidian
If $ARGUMENTS is obsidian:
Step 1 — Load config:
Check .vibe-learn/obsidian.json, then ~/.vibe-learn/obsidian.json.
If no config is found:
- Ask the user: "What is the path to your Obsidian vault? (e.g. /Users/me/MyVault)"
- Ask: "Which subfolder should vibe-learn notes go in? (default: Development/Sessions)"
- Ask: "Save this config globally for all projects (
~/.vibe-learn/obsidian.json) or just for this project (.vibe-learn/obsidian.json)? [global/project, default: global]" - Write the config to the chosen location (creating the directory with
mkdir -pif needed):
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.
- 4d ago First seen · 162 lines · 24 tokens per session scan B f6d332f7d9a5
digest is a command published in the GitHub repository gkaria/vibe-learn (54 stars, last pushed 7d ago), licensed MIT. It adds 24 tokens to every session and 1,445 once invoked, about $0.0001 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 commands, from other repositories
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
no-vibe
Enter no-vibe mode in OpenCode (tutor mode, no direct project file writes).
teach-me-testing
Teach testing progressively through structured sessions. Use when user says ""lets learn testing"" or ""I want to study test practices"".
setup-bigquery.es
Command "setup-bigquery.es" from minicoohei/ai-agent-camp, covering configuración de autenticación bigquery / gcp, step 0: verificar el progreso de configuración, lo que hará en esta sesión, verificación de preparación and step 1: instalación de gcloud cli.
setup-content
Lesson command — 教材コンテンツの初回セットアップ.