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.
git clone --depth 1 https://github.com/ankushdixit/claude-pluginsWrote 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/ankushdixit/claude-plugins/learn)<a href="https://agentmods.dev/commands/ankushdixit/claude-plugins/learn"><img src="https://agentmods.dev/badge/commands/ankushdixit/claude-plugins/learn/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ankushdixit/claude-plugins/learn"><img src="https://agentmods.dev/badge/commands/ankushdixit/claude-plugins/learn.svg" alt="Reviewed on agentmods" width="80" 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.00006 | $0.01176 |
| Opus 5.5 | $0.00002 | $0.00470 |
| Sonnet 5.5 | $0.00001 | $0.00235 |
| Haiku 4.5 | $0.00001 | $0.00118 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Learning Capture
Record insights, gotchas, and best practices discovered during development.
Step 1: Analyze Session and Generate Learning Suggestions
Review what was accomplished in the current session:
- What code was written/changed
- What problems were solved
- What patterns or approaches were used
- What technical insights were discovered
- What gotchas or edge cases were encountered
Generate 2-3 learning suggestions based on the session work. Good learnings are:
- Specific technical insights (not generic)
- Actionable and memorable
- About tools, patterns, or gotchas encountered
- Clear and concise (1-2 sentences)
Step 2: Ask User to Select Learnings
Use AskUserQuestion with multi-select to let user choose learnings:
Question: Select Learnings from This Session
- Question: "I've identified some potential learnings from this session. Select all that apply, or add your own:"
- Header: "Learnings"
- Multi-select: true
- Options (up to 4 total):
- Option 1: [Your generated learning suggestion 1]
- Option 2: [Your generated learning suggestion 2]
- Option 3: [Your generated learning suggestion 3] (if applicable)
- Option 4: [Your generated learning suggestion 4] (if applicable)
Example Options:
- "TypeScript enums are type-safe at compile time but add runtime overhead"
- "Zod schemas can be inferred as TypeScript types using z.infer<>"
- "React useCallback dependencies must include all values used inside the callback"
Step 3: For Each Selected Learning, Determine Category
For each learning the user selected (or entered), automatically suggest the most appropriate category:
Categories:
architecture_patterns- Design decisions, patterns used, architectural approachesgotchas- Edge cases, pitfalls, bugs discoveredbest_practices- Effective approaches, recommended patternstechnical_debt- Areas needing improvement, refactoring neededperformance_insights- Optimization learnings, performance improvementssecurity- Security-related discoveries, vulnerabilities fixed
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.
- 1mo ago First seen · 149 lines · 6 tokens per session scan A 63810c63ffc6
learn is a command published in the GitHub repository ankushdixit/claude-plugins (3 stars, last pushed 9mo ago), licensed MIT. It adds 6 tokens to every session and 1,176 once invoked, about $0.0000 per session on Opus 5.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
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-0-8
A Japanese-language command that displays the current project setup progress.
setup-m365cli.es
Lesson command — Setup de M365 CLI.
prep-role
Deep prep for a specific role's interview process. The user wants to know what to expect, how to win, and what kills candidates at their level.
start-1
A guided beginner course for product managers learning Claude Code, a coding assistant that works from the command line.