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/siniyayousuf/everything_claudecode/learngit clone --depth 1 https://github.com/SiniyaYousuf/everything_claudecodeWrote 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/siniyayousuf/everything_claudecode/learn)<a href="https://agentmods.dev/commands/siniyayousuf/everything_claudecode/learn"><img src="https://agentmods.dev/badge/commands/siniyayousuf/everything_claudecode/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.00008 | $0.00324 |
| Opus 5 | $0.00004 | $0.00162 |
| Sonnet 5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00032 |
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.
This is a copy
100% identical to learn — 0 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.
What it actually says
Learn Command
Extract patterns, learnings, and reusable insights from the current session: $ARGUMENTS
Your Task
Analyze the conversation and code changes to extract:
- Patterns discovered - Recurring solutions or approaches
- Best practices applied - Techniques that worked well
- Mistakes to avoid - Issues encountered and solutions
- Reusable snippets - Code patterns worth saving
Output Format
Patterns Discovered
Pattern: [Name]
- Context: When to use this pattern
- Implementation: How to apply it
- Example: Code snippet
Best Practices Applied
- [Practice name]
- Why it works
- When to apply
Mistakes to Avoid
- [Mistake description]
- What went wrong
- How to prevent it
Suggested Skill Updates
If patterns are significant, suggest updates to:
skills/coding-standards/SKILL.mdskills/[domain]/SKILL.mdrules/[category].md
Instinct Format (for continuous-learning-v2)
{
"trigger": "[situation that triggers this learning]",
"action": "[what to do]",
"confidence": 0.7,
"source": "session-extraction",
"timestamp": "[ISO timestamp]"
}
TIP: Run /learn periodically during long sessions to capture insights before context compaction.
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 · 62 lines · 8 tokens per session scan A 67b1f6181411
learn is a command published in the GitHub repository SiniyaYousuf/everything_claudecode (14 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 324 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to learn, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
neo-review
Get Neo's code review with semantic matching against past findings in memory. Use on a diff or module before merge, especially where earlier mistakes in this codebase are likely to recur. Skip for formatting, lint-catchable issues, and single-line changes.