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 not0lucky/tubescout --skill yt-playbookgit clone --depth 1 https://github.com/not0lucky/tubescoutWrote 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/not0lucky/tubescout/yt-playbook)<a href="https://agentmods.dev/skills/not0lucky/tubescout/yt-playbook"><img src="https://agentmods.dev/badge/skills/not0lucky/tubescout/yt-playbook/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/not0lucky/tubescout/yt-playbook"><img src="https://agentmods.dev/badge/skills/not0lucky/tubescout/yt-playbook.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.00087 | $0.00623 |
| Opus 5 | $0.00044 | $0.00311 |
| Sonnet 5 | $0.00017 | $0.00125 |
| Haiku 4.5 | $0.00009 | $0.00062 |
Grade A, and why
yt-playbook 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 12d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
yt-playbook
Tutorials bury 10 minutes of instructions in 25 minutes of talk. Extract the instructions, keep the hard-won details, drop the filler.
Process
- Fetch.
get_video+get_transcript. Note publish date immediately — a 2024 tutorial for a fast-moving tool needs a freshness warning per step that may have changed (UI labels, flags, pricing). - Extract the procedure. Ordered steps as the creator actually performs them, not as they summarize them. For each step capture verbatim: commands, filenames, settings values, versions, URLs, prices, keyboard paths ("Settings → API → …").
- Harvest the gold in passing. The most valuable lines in any tutorial are asides: "make sure you…", "this failed for me until…", "don't use X, it breaks Y". Collect these as a Gotchas section — they're why the playbook beats the video.
- Adapt to the user. Check the conversation for the user's actual stack, OS, and project. Translate where they differ from the video (their package manager, their cloud, their framework version). Mark every adaptation explicitly as yours, not the creator's.
- Deliver. Prerequisites → numbered steps (with exact values) → gotchas → verification ("you know it worked when…") → what the video skipped or hand-waved.
Rules
- Cite only URLs returned by tubescout tools in this conversation — never write a YouTube URL or video ID from memory.
- Never invent a command the creator didn't give; if a step is vague in the video, say "creator hand-waves this — likely X" and mark it as inference.
- Multi-part series: ask before fetching more than 3 videos.
- If the video is content-free hype with no real procedure, say so in one line and stop — don't fabricate a playbook.
Troubleshooting
- Tools missing → connect tubescout:
claude mcp add --scope user tubescout -- npx -y tubescout,codex mcp add tubescout -- npx -y tubescout, or the OpenCodeopencode.jsonmcp entry. - Long video (>60k chars) → page through
get_transcriptwithoffsetCharsuntilhasMoreis false; don't build the playbook from a partial read.
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.
- 12d ago First seen · 42 lines · 87 tokens per session scan A 7c91fb2d9a72
yt-playbook is a skill published in the GitHub repository not0lucky/tubescout (0 stars, last pushed 16d ago), licensed MIT. It adds 87 tokens to every session and 623 once invoked, about $0.0004 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-31.
Other skills, from other repositories
local-rag-search
Efficiently perform web searches using the mcp-local-rag server with semantic similarity ranking. Use this skill when you need to search the web for current information, research topics across multiple sources, or gather context from the internet without using external APIs. This skill teaches effective use of…
octave-literacy
LLM-native structured communication format. Teaches OCTAVE syntax rules, canonical forms, and warning prevention for zero-error .oct.md authoring.
greentext
Explain system behavior, request flows, architecture, or implementation logic as short 4chan-style greentext lines. Use when the user asks for a step-by-step explanation, says "explain the logic", asks for "greentext", or wants terse sequential reasoning with each line starting with >.
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis with two-column tables. Left column preserves the chapter content; right column maps every idea to the reader's actual life using brain context. Output is a single brain page at media/books/ -personalized plus an optional PDF via brain-pdf.
rtfm
Verify claims against primary sources before writing code or docs. Read the actual API, run the actual command, check the actual docs. Do not guess. Do not assume. Do not ship until verified.
courses
GetCourse management - users, deals, student creation.