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/marshall0524/everythingclaudecode/learngit clone --depth 1 https://github.com/marshall0524/everythingclaudecodeWhat 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 2d 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.
- 2d ago First seen · 62 lines · 8 tokens per session scan A 67b1f6181411
learn is a command published in the GitHub repository marshall0524/everythingclaudecode (35 stars, last pushed 1mo 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.