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/smrafiz/claude-superchargerWrote 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/smrafiz/claude-supercharger/learn)<a href="https://agentmods.dev/commands/smrafiz/claude-supercharger/learn"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/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.00411 |
| Opus 5 | $0.00000 | $0.00205 |
| Sonnet 5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
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 7d 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
Record an explicit user-stated rule. Arguments: $ARGUMENTS
Capture $ARGUMENTS as a high-confidence project rule that will be surfaced on future prompts.
Action:
-
Validate —
$ARGUMENTSmust contain a clear directive (verb + object). If empty or vague (less than 4 words, no verb), respond:Usage: /learn <rule>. Example: /learn always use pnpm in this project. -
Append a lesson record to
.claude/supercharger/lessons.jsonl(per-project, walk up from cwd to find the project root):
{"sig":"<user rule>","fix":"<rule restated as instruction>","files":[],"lesson":"<rule>","recall":"<lowercase tokens of rule, deduped, joined by space>","ts":"<ISO timestamp>","source":"user-explicit"}
-
Optionally update
.supercharger.json— if ahintsfield exists, append the rule to it (newline-separated). If no.supercharger.json, do not create one (out of scope). -
Confirm — print:
✓ Recorded: <rule>
→ lessons.jsonl (1 entry added)
→ will surface on prompts containing: <top 3 keywords>
Do not:
- Fabricate context the user did not state.
- Apply the rule retroactively to past code.
- Modify any other config file.
Do:
- Use the same JSONL schema as
hooks/lesson-record.shfor compatibility withhooks/lesson-recall.sh(Jaccard match). - Mark
source: "user-explicit"so future analysis can distinguish from auto-captured lessons. - Use lowercase tokens of length ≥ 3, deduped and sorted, for the
recallfield.
Stop after the confirmation message. Do not ask follow-up questions.
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.
- 7d ago First seen · 36 lines · 0 tokens per session scan A 5e4cdc852e25
learn is a command published in the GitHub repository smrafiz/claude-supercharger (11 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 411 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
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.
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.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.