Borrowing it
Nothing to install: this file belongs to sakrut/ai-code-graph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sakrut/ai-code-graph/main/.claude/commands/tm/learn.mdgit clone --depth 1 https://github.com/sakrut/ai-code-graphWrote 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/sakrut/ai-code-graph/learn)<a href="https://agentmods.dev/commands/sakrut/ai-code-graph/learn"><img src="https://agentmods.dev/badge/commands/sakrut/ai-code-graph/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/sakrut/ai-code-graph/learn"><img src="https://agentmods.dev/badge/commands/sakrut/ai-code-graph/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.00000 | $0.00691 |
| Opus 5.5 | $0.00000 | $0.00276 |
| Sonnet 5.5 | $0.00000 | $0.00138 |
| Haiku 4.5 | $0.00000 | $0.00069 |
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.
This is a copy
94% identical to learn — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Learn
Arguments: $ARGUMENTS Learn about Task Master capabilities through interactive exploration.
Arguments: $ARGUMENTS
Interactive Task Master Learning
Based on your input, I'll help you discover capabilities:
1. What are you trying to do?
If $ARGUMENTS contains:
- "start" / "begin" → Show project initialization workflows
- "manage" / "organize" → Show task management commands
- "automate" / "auto" → Show automation workflows
- "analyze" / "report" → Show analysis tools
- "fix" / "problem" → Show troubleshooting commands
- "fast" / "quick" → Show efficiency shortcuts
2. Intelligent Suggestions
Based on your project state:
No tasks yet?
You'll want to start with:
1. /project:task-master:init <prd-file>
→ Creates tasks from requirements
2. /project:task-master:parse-prd <file>
→ Alternative task generation
Try: /project:task-master:init demo-prd.md
Have tasks? Let me analyze what you might need...
- Many pending tasks? → Learn sprint planning
- Complex tasks? → Learn task expansion
- Daily work? → Learn workflow automation
3. Command Discovery
By Category:
- 📋 Task Management: list, show, add, update, complete
- 🔄 Workflows: auto-implement, sprint-plan, daily-standup
- 🛠️ Utilities: check-health, complexity-report, sync-memory
- 🔍 Analysis: validate-deps, show dependencies
By Scenario:
- "I want to see what to work on" →
/project:task-master:next - "I need to break this down" →
/project:task-master:expand <id> - "Show me everything" →
/project:task-master:status - "Just do it for me" →
/project:workflows:auto-implement
4. Power User Patterns
Command Chaining:
/project:task-master:next
/project:task-master:start <id>
/project:workflows:auto-implement
Smart Filters:
/project:task-master:list pending high
/project:task-master:list blocked
/project:task-master:list 1-5 tree
Automation:
/project:workflows:pipeline init → expand-all → sprint-plan
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 · 106 lines · 0 tokens per session scan A 494976da16fb
learn is a command published in the GitHub repository sakrut/ai-code-graph (3 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 691 tokens. A static security scan graded it A with 0 findings. It is 94% identical to learn, differing in 7 lines, and is treated as a copy.
Other commands, from other repositories
onboard
Create an onboarding plan and materials for a new team member.
gsd:help
Show available GSD commands and usage guide.
train-executor
Generate an executor onboarding playbook from a person's Freedom Path DELEGATE bucket. Produces SOPs in the person's voice, a training curriculum, and outdated-material flags. Non-technical-friendly — designed for Claude Desktop + Cowork usage.
hatch3r-onboard
Generate a comprehensive onboarding guide for a new developer joining the project -- spawn parallel researchers to analyze codebase structure, architecture, and conventions, then produce a tailored onboarding document with setup instructions, architecture walkthrough, coding conventions, key workflows, tribal…
onboard
Parallel codebase onboarding — fires code-explorer + architect + doc-updater simultaneously. Understand any codebase in 15 minutes instead of 3 days.
onboard-project
Explain an unfamiliar project to whoever takes it over: purpose, modules, critical flows, setup and tests, evidenced risks, active decisions, real unknowns and a first scoped work plan. Changes nothing in the project. TRIGGER WHEN: the user is new to a project, takes one over, or asks to be walked through it. DO NOT…