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/learngit clone --depth 1 https://github.com/gkaria/vibe-learnWhat 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.00021 | $0.01377 |
| Opus 5 | $0.00010 | $0.00688 |
| Sonnet 5 | $0.00004 | $0.00275 |
| Haiku 4.5 | $0.00002 | $0.00138 |
Grade B, and why
learn 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 2d 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.
**Knowledge ledger check (all modes):** if `.vibe-learn/knowledge.json` exists, run the knowledge helper's `due` command via Bash (`bash ~/.vibe-learn/scripts/knowledge.sh due`; if that path doesn't exist, use the `scrip How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read .vibe-learn/session-log.jsonl to understand what has happened in this session.
Knowledge ledger check (all modes): if .vibe-learn/knowledge.json exists, run the knowledge helper's due command via Bash (bash ~/.vibe-learn/scripts/knowledge.sh due; if that path doesn't exist, use the scripts/knowledge.sh next to the bootstrap.sh your vibe-learn hooks point at in .claude/settings.local.json or ~/.claude/settings.json, or bash scripts/knowledge.sh due when working in the vibe-learn repo itself). If a due concept was also touched in this session's log, open your response with a single heads-up line, e.g. "Heads up: this session touched JWT refresh tokens again — you marked that shaky on July 11. Want a quick recap first, or /quiz review?" At most one such line, and never let it block or replace the actual answer. If the ledger or helper is missing, skip this silently.
Parse $ARGUMENTS to determine the mode:
Mode: obsidian:recall <topic>
If $ARGUMENTS starts with obsidian:recall:
Extract the topic (everything after obsidian:recall). If no topic is given, ask the user what they want to recall.
- Load the Obsidian config: check
.vibe-learn/obsidian.jsonfirst, then~/.vibe-learn/obsidian.json. If neither exists, run the config setup flow (ask vault path, subfolder, global vs project save location) before proceeding — same flow as theobsidianmode below. - Construct the search path:
<vault_path>/<subfolder>/ - Search that directory for markdown files matching the topic — search across filenames, headings (
#), body text, and frontmatter tags using the Grep tool. - Read up to 5 of the most relevant matching files.
- Synthesize a summary covering:
- Which sessions touched this topic and when (use the
datefrontmatter field) - Key decisions and patterns related to the topic
- Any unchecked
- [ ]items in "Things to Study" sections on this topic - Connections or progressions across sessions (e.g., "You first set this up on March 2nd, then extended it on April 5th")
- Which sessions touched this topic and when (use the
- Present the summary to the user. Do not write any file.
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.
- 2d ago First seen · 111 lines · 21 tokens per session scan B 19cbdecfdd5b
learn is a command published in the GitHub repository gkaria/vibe-learn (54 stars, last pushed 6d ago), licensed MIT. It adds 21 tokens to every session and 1,377 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.