A command that reviews the current coding session and identifies useful problem-solving patterns to save for later.

Use it after solving a difficult error, discovering a project convention, or finding a useful library workaround. It creates a skill file describing the problem, solution, example, and when to use it.

It helps you avoid repeating the same debugging work by turning successful techniques and workarounds into reusable instructions.

learn — Command by zhmxiaowo

Install

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.

agentmods

npx agentmods add commands/zhmxiaowo/opencode-simple/learn

Clone the repo

git clone --depth 1 https://github.com/zhmxiaowo/opencode-simple

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 394 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 89% copy Near-identical to another mod in the catalogue.

Token cost

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.00015	$0.00394
Opus 5	$0.00008	$0.00197
Sonnet 5	$0.00003	$0.00079
Haiku 4.5	$0.00002	$0.00039

Measured yesterday against content hash 013c3f633657, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

Origin

This is a copy

89% identical to learn — 4 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.

.opencode/commands/learn.md · 75 lines

What it actually says

/learn - Extract Reusable Patterns

Analyze the current session and extract any patterns worth saving as skills.

Trigger

Run /learn at any point during a session when you've solved a non-trivial problem.

What to Extract

Look for:

Error Resolution Patterns
- What error occurred?
- What was the root cause?
- What fixed it?
- Is this reusable for similar errors?
Debugging Techniques
- Non-obvious debugging steps
- Tool combinations that worked
- Diagnostic patterns
Workarounds
- Library quirks
- API limitations
- Version-specific fixes
Project-Specific Patterns
- Codebase conventions discovered
- Architecture decisions made
- Integration patterns

Output Format

Create a skill file at ~/.claude/skills/learned/[pattern-name].md:

# [Descriptive Pattern Name]

**Extracted:** [Date]
**Context:** [Brief description of when this applies]

## Problem
[What problem this solves - be specific]

## Solution
[The pattern/technique/workaround]

## Example
[Code example if applicable]

## When to Use
[Trigger conditions - what should activate this skill]

Process

Review the session for extractable patterns
Identify the most valuable/reusable insight
Draft the skill file
Ask user to confirm before saving
Save to ~/.claude/skills/learned/

Notes

Don't extract trivial fixes (typos, simple syntax errors)
Don't extract one-time issues (specific API outages, etc.)
Focus on patterns that will save time in future sessions
Keep skills focused - one pattern per skill

Changes

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.

yesterday First seen · 75 lines · 15 tokens per session scan A 013c3f633657

Subscribe to this mod's changes

learn is a command published in the GitHub repository zhmxiaowo/opencode-simple (2 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 394 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to learn, differing in 4 lines, and is treated as a copy.

Building agents

verify

Adversarial spec-vs-implementation verification for a completed task. Dispatches the spec-mentor subagent with fresh context (no anchoring bias), parses its verdict (PASS / DRIFT / NEEDS-MARTY), and updates the verification queue. The v7.4.0 architectural replacement for a dedicated "mentor session.".

MartyBonacci/specswarm · 68 tokens

learn