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 agentmods add skills/sammcj/agentic-coding/extract-wisdomnpx skills add sammcj/agentic-coding --skill extract-wisdomgit clone --depth 1 https://github.com/sammcj/agentic-codingWhat 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.00043 | $0.04025 |
| Opus 5 | $0.00022 | $0.02013 |
| Sonnet 5 | $0.00009 | $0.00805 |
| Haiku 4.5 | $0.00004 | $0.00402 |
Grade A, and why
extract-wisdom 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.
How it starts
The opening of the file, as written. The whole thing — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wisdom Extraction
Script paths below use ${CLAUDE_SKILL_DIR} to refer to this skill's directory.
Default location for Claude Code: ~/.claude/skills/extract-wisdom/
Workflow
Step 1: Identify Source and Acquire Content
Determine the source type and read the corresponding reference file:
- YouTube URL (contains youtube.com or youtu.be): Read
references/source-youtube.mdand follow its instructions. - Web URL or local file: Read
references/source-web-text.mdand follow its instructions.
After acquiring the source content, return here for Step 2. If the user provided additional instructions about the level of detail or focus areas, apply those throughout the analysis.
Step 2: Analyse and Extract Wisdom
IMPORTANT: Avoid signal dilution, context collapse, quality degradation and degraded reasoning for future understanding of the content. Keep the signal-to-noise ratio high. Preserve domain insights while excluding filler or fluff.
Perform analysis on the content, extracting:
1. Key Insights
- Identify the main ideas, core concepts, and central arguments
- Extract fundamental learnings and important revelations
- Highlight expert advice, best practices, or recommendations
- Note any surprising or counterintuitive information
- Diagram(s) to explain complex relationships, workflows or concepts
2. Notable Quotes
- Extract memorable, impactful, or particularly well-articulated statements
- Include context for each quote when relevant
- Focus on quotes that encapsulate key ideas or provide unique perspectives
- If the content itself quotes other sources, ensure those quotes are also captured
- If you are adding quotes do not add more than 3-5 quotes unless requested by the user
- Preserve the original wording exactly, except correct American spellings to Australian English
3. Structured Summary
- Create hierarchical organisation of content
- Break down into logical sections or themes
- Provide clear section headings that reflect content structure
- Include high-level overview followed by detailed breakdowns
- Note any important examples, case studies, or demonstrations
What ships with it
11 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.
- .gitignore 116 B
- CLAUDE.md 696 B
- references/build-ebook.md 1.2 KB
- references/source-web-text.md 2.0 KB
- references/source-youtube.md 1.8 KB
- scripts/transcribe.py 9.6 KB runs code
- scripts/wisdom.py 125 KB runs code
- styles/wisdom-epub.css 7.1 KB
- styles/wisdom-index.html 52 KB
- styles/wisdom-pdf.css 7.7 KB
- styles/wisdom-pdf.html5 343 B
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 · 357 lines · 43 tokens per session scan A 7112cd255fef
extract-wisdom is a skill published in the GitHub repository sammcj/agentic-coding (158 stars, last pushed 7d ago), licensed Apache-2.0. It adds 43 tokens to every session and 4,025 once invoked, about $0.0002 per session on Opus 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-30.
Other skills, from other repositories
yann-lecun-filosofia
Sub-skill filosófica e pedagógica de Yann LeCun.
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…
docs-reviewer
Review documentation drafts for voice consistency, structure, and terminology before PR submission. Use after completing a draft, when checking if docs are ready to ship, or automatically after docs-writer produces output. Also triggers on "review this draft", "check my docs", "is this ready to ship", "review before…
docs-planner
Identify documentation gaps and prioritize the docs backlog. Use when planning a docs improvement sprint, after signals surface repeated friction, when new SDK features ship without docs, or for periodic health assessment. Also triggers on "plan docs work", "what docs need writing", "prioritize the backlog", "docs…
skill-creator
Create, refine, and benchmark agent skills. Use when building a new skill, updating an existing one, running evals, checking trigger quality, or improving a skill description.
session-checkpoint
Re-orient a long, dense, or interruption-prone agent session without replacing the underlying evidence. Use when the user asks for a recap, orientation, simple teaching explanation, or spoken summary; when a session has accumulated many turns or tool calls; before context compaction; or when a Brief-Spec hook says a…