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/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/learn)<a href="https://agentmods.dev/commands/xrensiu/claude-code-forge/learn"><img src="https://agentmods.dev/badge/commands/xrensiu/claude-code-forge/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/xrensiu/claude-code-forge/learn"><img src="https://agentmods.dev/badge/commands/xrensiu/claude-code-forge/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.01466 |
| Opus 5.5 | $0.00000 | $0.00586 |
| Sonnet 5.5 | $0.00000 | $0.00293 |
| Haiku 4.5 | $0.00000 | $0.00147 |
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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/learn Command
独特功能！ Extract reusable patterns from the current session into Skills or Rules.
Purpose
Traditional workflow: Problem solved → Knowledge lost
With /learn: Problem solved → Pattern extracted → Knowledge preserved
This command analyzes the current conversation to identify:
- Recurring patterns
- Novel solutions
- Best practices discovered
- Anti-patterns avoided
Usage
/learn [output-type] [options]
Arguments
| Argument | Required | Default | Description |
|---|---|---|---|
| output-type | No | auto | What to create: skill, rule, pattern, auto |
Options
| Option | Description |
|---|---|
| --name | Name for the extracted artifact |
| --description | Description of what was learned |
| --preview | Show what would be extracted without saving |
| --append | Append to existing skill/rule instead of creating new |
Examples
# Auto-detect what to extract
/learn
# Extract as a new skill
/learn skill --name "handling-webhook-retries"
# Extract as a rule
/learn rule --name "api-versioning-pattern"
# Preview without saving
/learn --preview
# Add to existing skill
/learn --append skills/error-handling
What Gets Extracted
From Debugging Sessions
Pattern: "Root cause analysis for race conditions"
Extracted:
- Reproduction steps
- Diagnostic commands used
- Solution approach
- Prevention strategies
From Implementation Sessions
Pattern: "OAuth2 flow implementation"
Extracted:
- Architecture decisions
- Security considerations
- Error handling patterns
- Testing strategies
From Review Sessions
Pattern: "Common TypeScript pitfalls"
Extracted:
- Anti-patterns found
- Recommended alternatives
- Detection commands
Output Types
skill
Creates a new Skill in .claude/skills/:
---
name: [extracted-name]
description: [Use when...] Extracted from session on [date].
---
# [Skill Name]
## Context
[Why this pattern emerged]
## Pattern
[The reusable workflow/approach]
## Examples
[Code from the session]
## Anti-patterns
[What to avoid, if discovered]
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 · 285 lines · 0 tokens per session scan A 4209479148cb
learn is a command published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,466 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-09-05.
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.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.