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/superhero-tech/super-brain/youtubenpx skills add superhero-tech/super-brain --skill youtubegit clone --depth 1 https://github.com/superhero-tech/super-brainWrote 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/superhero-tech/super-brain/youtube)<a href="https://agentmods.dev/skills/superhero-tech/super-brain/youtube"><img src="https://agentmods.dev/badge/skills/superhero-tech/super-brain/youtube.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.01015 |
| Opus 5 | $0.00023 | $0.00508 |
| Sonnet 5 | $0.00009 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
youtube 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 4d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YouTube Video Summary
Turns a YouTube video into a structured note, then compiles that note into a wiki page in Knowledge.
When to use
- You want a video turned into a clean note with metadata and key ideas
- For tutorials the output is a step-by-step guide, not a summary
Requirements
This skill pulls metadata and subtitles with yt-dlp. Install it once:
brew install yt-dlp # macOS
pip install yt-dlp # everywhere else
Without yt-dlp the skill still works, just slower: take the video ID from the URL and search the web for the metadata, then ask the human to paste the transcript from YouTube's transcript panel. Say which route you are taking so they know why it takes longer.
How to invoke
/youtube https://youtube.com/watch?v=...- "Make a note from this video: [URL]"
How it works
1. Pull the metadata
yt-dlp --skip-download --print "%(title)s|||%(channel)s|||%(upload_date)s|||%(description).500s" "$ARGUMENTS"
If yt-dlp fails: extract the video ID from the URL and use web search.
2. Get the transcript
yt-dlp --skip-download --write-auto-subs --sub-langs "en" --sub-format "vtt" -o "/tmp/yt_transcript" "$ARGUMENTS"
Add more languages to --sub-langs when you need them. If it fails, ask the user to paste the transcript from YouTube.
3. Classify the video
- Tutorial/Explainer: walkthrough, demo, how-to -> output a step-by-step guide
- Idea/Opinion: thesis, interview, perspective -> output key ideas plus quotes
4. Generate the note
YAML frontmatter:
---
date: YYYY-MM-DD
title: "Video Title"
author: Channel Name
source: [YouTube URL]
topics:
- topic-1
- topic-2
source_type: video
---
This is the frontmatter of the source note that lands in 2-Inbox/ and later 5-Raw/. It is not wiki-page frontmatter - wiki pages use type: concept | entity. Do not copy this block onto the wiki page.
For tutorials:
# Title
## What this covers
[1-2 sentences]
## Step-by-Step
### Step 1: [Action]
[What to click, type, configure. Imperative.]
## Tips & Gotchas
- Practical notes and limitations
## Source
[URL]
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.
- 4d ago First seen · 138 lines · 46 tokens per session scan A 99774bf3d537
youtube is a skill published in the GitHub repository superhero-tech/super-brain (114 stars, last pushed 9d ago), licensed MIT. It adds 46 tokens to every session and 1,015 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…