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/tomdwipo/claude-soul/learngit clone --depth 1 https://github.com/tomdwipo/claude-soulWrote 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/tomdwipo/claude-soul/learn)<a href="https://agentmods.dev/commands/tomdwipo/claude-soul/learn"><img src="https://agentmods.dev/badge/commands/tomdwipo/claude-soul/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.1 | $0.00000 | $0.00252 |
| Opus 5 | $0.00000 | $0.00126 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
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 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.
What it actually says
/learn — Distil a correction into a principle (or rule)
Run the engine in .docs/principles/how-to-learn.md
on the most recent correction(s) in this session (or on $ARGUMENTS if given).
Steps:
- Identify the concrete correction (quote it).
- Find the root cause (why), not the symptom.
- Confirm it generalises (applies 3+ times) — else stop and say so.
- Scan
.docs/principles/README.md+.docs/common-issues/for an existing entry to sharpen/merge instead of adding a sibling. - FORK (principle-default): a compile/test/lint/build result settles it → RULE
(
.docs/common-issues/+ catalog row); judgment/taste → PRINCIPLE (.docs/principles/+ index row); unsure → principle. - Write the file in the canonical shape; keep it tight.
- Show the exact diff (new/edited files + index/catalog rows) and STOP for review. Do not commit unless the user says so.
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.
- 6d ago First seen · 18 lines · 0 tokens per session scan A 59c5ab6104b8
learn is a command published in the GitHub repository tomdwipo/claude-soul (24 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 252 tokens. 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-30.
Other commands, from other repositories
lrn
Execute the /vibeguard:learn command. $ARGUMENTS.
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.
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.
start-10-1
Command "start-10-1" from minicoohei/ai-agent-camp, covering 🎓 lesson 10-1: clasp基本・gasプロジェクト管理, 📍 このセッションでやること, 🎯 準備チェック, 🚀 step 1: claspのインストールと apps script api の確認 and 🚀 step 2: google認証.
start-13-4.en
Welcome to Lesson 13-4: Landing Page Implementation!