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/znlnzi/claude-config-studio/learngit clone --depth 1 https://github.com/znlnzi/claude-config-studioWrote 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/znlnzi/claude-config-studio/learn)<a href="https://agentmods.dev/commands/znlnzi/claude-config-studio/learn"><img src="https://agentmods.dev/badge/commands/znlnzi/claude-config-studio/learn.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.00014 | $0.00297 |
| Opus 5 | $0.00007 | $0.00148 |
| Sonnet 5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
learn 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 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.
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
/learn - 提取学习成果
从当前会话中提取可重用的模式和经验。
工作流
- 回顾会话 - 分析当前会话中解决的问题
- 提取模式 - 识别可重用的解决方案
- 格式化 - 按标准格式记录
- 保存 - 写入学习文件
提取内容
- 错误解决方法: 问题原因和修复方案
- 调试技巧: 有效的调试方法和工具组合
- 变通方案: 库的怪癖或 API 限制的解决办法
- 架构模式: 项目特定的设计模式
学习记录格式
## [模式名称]
### 问题
[问题描述]
### 解决方案
[解决方案描述]
### 代码示例
[相关代码]
### 适用条件
[何时使用这个模式]
保存位置
学习记录保存到 .claude/learnings/ 目录。
质量过滤
排除以下内容：
- 简单的拼写错误修复
- 一次性的环境问题
- 第三方服务的临时故障
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 · 50 lines · 14 tokens per session scan A 25d2b28a9117
learn is a command published in the GitHub repository znlnzi/claude-config-studio (0 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 297 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
context-stats
Display context window usage and token statistics.
thoughts_init
Initialize thoughts system for current repository.
handoff
Create a handoff document for seamless session continuity.
meetings-list
List recent meetings and voice memos. Use when the user asks "what meetings did I have", "show my recent recordings", "any meetings today", "list my voice memos", or wants an overview of their meeting history. Also use when they need to find a specific meeting by browsing rather than searching.
handoff
Create, accept, or update the persistent .context/ai-handoff.md state shared by AI sessions and machines. Use when continuing in a new Claude or Codex session, transferring work between clients, or recording ownership and restart state.
meetings-search
Search meeting transcripts and voice memos for people, topics, decisions, commitments, or remembered ideas. Use when the user asks what was discussed, decided, or said across their meeting history. Not for preparing an upcoming meeting; use $meetings-prep.