Borrowing it
Nothing to install: this file belongs to dixus/claudeframework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dixus/claudeframework/main/.claude/skills/learn/SKILL.mdgit clone --depth 1 https://github.com/dixus/claudeframeworkWrote 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/dixus/claudeframework/learn)<a href="https://agentmods.dev/skills/dixus/claudeframework/learn"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/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/dixus/claudeframework/learn"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/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.00038 | $0.01838 |
| Opus 5.5 | $0.00015 | $0.00735 |
| Sonnet 5.5 | $0.00008 | $0.00368 |
| Haiku 4.5 | $0.00004 | $0.00184 |
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 2mo 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process new material from .claude/references/ and propose concrete changes to skills and rules. No intermediate knowledge files — findings route directly to actionable proposals.
URL ingestion (when $ARGUMENTS is a URL)
If $ARGUMENTS starts with http:// or https://, treat it as a URL to ingest:
- WebFetch the URL and extract the main content (article text, README, docs — skip nav/ads/boilerplate)
- Generate a slug from the page title or URL path (e.g.
claude-code-best-practices.md) - Write the extracted content as markdown to
references/blogs/<slug>.md - Log: "Saved → references/blogs/.md"
- Continue to the processing steps below — the new file will be picked up as unprocessed
This bridges the scout-learn pipeline: /scout produces "Worth investigating" URLs, and /learn <url> ingests them directly.
Idempotency rule — filesystem-based, read this first
Processed state is tracked on the filesystem — do NOT rely on the index table for deduplication:
- Blog files: physically moved to a
processed/subfolder - Repo directories: marked with an empty
processed/.donefile inside the repo dir (too large to move)
- Scan the filesystem for unprocessed candidate items:
references/blogs/— every file directly in this folder (NOT insideprocessed/)references/repos/— every subdirectory that does NOT have aprocessed/marker file inside it (i.e.,references/repos/<dir>/processed/.donedoes not exist)- Ignore
references/index.mdand anyprocessed/subfolders
- If there are no new items, skip to Skill review below.
Processing steps (only for unprocessed items)
For blog/article files (individual files in references/blogs/):
- Read the full content. For PDF files, use the
pagesparameter to read in chunks of 20 pages (e.g.pages: "1-20", thenpages: "21-40") — do not attempt to read an entire large PDF at once. - Extract only actionable, durable insights — skip opinions, anecdotes, and general knowledge Claude already has
- For each insight, map it to a concrete change target:
- A specific skill file (
.claude/skills/<name>/SKILL.md) — what line/section to change - A rule file (
.claude/rules/<name>.md) — create new or update existing CLAUDE.md— if it's a project-wide convention- If an insight doesn't map to any file, discard it — it's not actionable
- A specific skill file (
- Tag each insight with the affected skills:
**Affects:** [skill1, skill2] - Immediately after processing, move the file into the
processed/subfolder:references/blogs/processed/<filename>
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.
- 2mo ago First seen · 109 lines · 38 tokens per session scan A 62fd59cfab49
learn is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,838 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-08-31.
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…