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 skills add wyattowalsh/agents --skill learngit clone --depth 1 https://github.com/wyattowalsh/agentsWrote 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/skills/wyattowalsh/agents/learn)<a href="https://agentmods.dev/skills/wyattowalsh/agents/learn"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/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/skills/wyattowalsh/agents/learn"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/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.00039 | $0.00887 |
| Opus 5.5 | $0.00016 | $0.00355 |
| Sonnet 5.5 | $0.00008 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00089 |
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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Learn — Capture and Route Project Knowledge
Record corrections, insights, and patterns. Route them to the correct instruction file. Apply kaizen principles to keep instructions lean and effective.
Dispatch
$ARGUMENTS |
Action |
|---|---|
"<correction text>" |
Route correction to appropriate instruction file |
review |
Show pending learnings and their frequency |
promote |
Promote high-frequency learnings (3+ occurrences) to instruction files |
audit |
Check for stale, contradictory, or duplicate learnings |
| Empty | Display usage summary |
References
| File | Purpose |
|---|---|
references/routing-rules.md |
Decision tree for where to route instruction changes |
references/kaizen-principles.md |
Error-proofing patterns, when to use hooks vs prose vs rules |
Routing Protocol
Route proposed updates to the correct target:
| Scope | Target |
|---|---|
| Cross-project conventions | instructions/global.md |
| Language-specific tooling | Convention skill (python-conventions, etc.) |
| Orchestration/parallelism | orchestrator skill body |
| Project-specific standards | Project's AGENTS.md |
| File-scoped enforcement | .claude/rules/<topic>.md |
| Skill behavior | The skill's own SKILL.md |
Routing Decision Steps
- Determine the scope: does this apply to all projects or just one?
- If cross-project, does it relate to a specific language or tool?
- If language-specific, route to the corresponding convention skill
- If general, route to
instructions/global.md - If project-only, route to the project's
AGENTS.md - If file-scoped enforcement only, create a
.claude/rules/entry
Kaizen Principles
- Incremental > revolutionary — Smallest viable change, verify before next
- Poka-yoke — Prefer hooks/tooling over prose instructions (error-proof by design)
- Standards work — Follow existing patterns, document what works
- JIT — Build only what is needed, optimize when measured
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/correction-routing.json 812 B
- evals/evals.json 2.1 KB
- evals/promote-mode.json 775 B
- evals/review-mode.json 594 B
- references/kaizen-principles.md 1.7 KB
- references/routing-rules.md 2.0 KB
- scripts/asset_toolkit/__init__.py 303 B runs code
- scripts/asset_toolkit/_shared.py 5.6 KB runs code
- scripts/asset_toolkit/common.py 3.0 KB runs code
- scripts/asset_toolkit/package.py 43 KB runs code
- scripts/asset_toolkit/validate_evals.py 11 KB runs code
- scripts/asset_toolkit/validate_hooks.py 13 KB runs code
- scripts/asset_toolkit/validate_skill.py 3.6 KB runs code
- scripts/check.py 1.5 KB runs code
- scripts/state.py 3.8 KB runs code
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 · 104 lines · 39 tokens per session scan A ec2b45232440
learn is a skill published in the GitHub repository wyattowalsh/agents (5 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 887 once invoked, about $0.0002 per session on Opus 5.5. 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-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…