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 agentproto/ts --skill youtubegit clone --depth 1 https://github.com/agentproto/tsWrote 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/agentproto/ts/youtube)<a href="https://agentmods.dev/skills/agentproto/ts/youtube"><img src="https://agentmods.dev/badge/skills/agentproto/ts/youtube/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/agentproto/ts/youtube"><img src="https://agentmods.dev/badge/skills/agentproto/ts/youtube.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.00045 | $0.01006 |
| Opus 5.5 | $0.00018 | $0.00402 |
| Sonnet 5.5 | $0.00009 | $0.00201 |
| Haiku 4.5 | $0.00005 | $0.00101 |
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 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YouTube — recon plan (InnerTube API)
Internal API: InnerTube —
POST https://www.youtube.com/youtubei/v1/<endpoint>?key=<INNERTUBE_API_KEY>&prettyPrint=false,
body { context: <INNERTUBE_CONTEXT>, ...params }. The web app uses this for
everything.
Config + auth (from the page)
INNERTUBE_API_KEY+INNERTUBE_CONTEXTlive inytcfg. Read in-page:;() => ({ key: ytcfg.get("INNERTUBE_API_KEY"), ctx: ytcfg.get("INNERTUBE_CONTEXT"), })- Public reads: often work with just key + context (no auth).
- Personalized / write (subscriptions, comments, like): need SAPISIDHASH
auth:
Authorization: SAPISIDHASH <ts>_<SHA1(ts + " " + SAPISID + " " + origin)>where SAPISID = theSAPISID(or__Secure-3PAPISID) cookie, origin =https://www.youtube.com, ts = unix seconds. Compute SHA-1 in-page (SubtleCrypto). Also sendX-Goog-AuthUser: 0,Origin, cookies (auto).
In-page fetch:
;async (endpoint, body) => {
const key = ytcfg.get("INNERTUBE_API_KEY")
const r = await fetch(
`/youtubei/v1/${endpoint}?key=${key}&prettyPrint=false`,
{
method: "POST",
headers: {
"content-type": "application/json" /* + SAPISIDHASH for writes */,
},
body: JSON.stringify({
context: ytcfg.get("INNERTUBE_CONTEXT"),
...body,
}),
}
)
return await r.json()
}
Endpoints to test
| Purpose | endpoint | params |
|---|---|---|
| Channel / home / playlist | browse |
browseId (channel UC…), params |
| Watch page → video + comments token | next |
videoId |
| Comments (+ who/likes) | next (continuation token from the watch next) |
continuation |
| Search | search |
query, params |
| Video metadata | player |
videoId |
| WRITE: comment | comment/create_comment / create_comment_reply |
createCommentParams |
| WRITE: like/dislike | like/like / like/dislike / like/removelike |
target.videoId |
| WRITE: subscribe | subscription/subscribe / unsubscribe |
channelIds |
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 · 99 lines · 45 tokens per session scan A 7bd735deaf3b
youtube is a skill published in the GitHub repository agentproto/ts (10 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 1,006 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
demo-recorder
Use when the user wants a scripted screen-recording demo video of a web app, a narration script or text-to-speech voice-over for one, or a dubbed cut.
playwright
Use when the task requires capturing or automating a real browser from the terminal.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
browser-tools
Safety rules over the upstream agent-browser skill (scraping ethics, auth, request pacing, local URLs). URL policy is the Claude Code sandbox's job when the operator enables it. Use for browser automation.
qa-screenshot
Screenshot a page (deploy preview or a dev server on localhost) in the sandbox's headless Chromium, look at it, and embed it in a task comment. Use to verify a visual change or record before/after evidence.
skill-creator-primer
You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill. Triggers include creating, editing, reviewing, or contributing to any part of an Agent Skill (description, frontmatter, body, references, scripts, trigger evals, conflicts, etc).