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 nikhilbhansali/claude-youtube-skills --skill youtube-competitor-analyzergit clone --depth 1 https://github.com/nikhilbhansali/claude-youtube-skillsWrote 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/nikhilbhansali/claude-youtube-skills/youtube-competitor-analyzer)<a href="https://agentmods.dev/skills/nikhilbhansali/claude-youtube-skills/youtube-competitor-analyzer"><img src="https://agentmods.dev/badge/skills/nikhilbhansali/claude-youtube-skills/youtube-competitor-analyzer/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/nikhilbhansali/claude-youtube-skills/youtube-competitor-analyzer"><img src="https://agentmods.dev/badge/skills/nikhilbhansali/claude-youtube-skills/youtube-competitor-analyzer.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.00117 | $0.00944 |
| Opus 5.5 | $0.00047 | $0.00378 |
| Sonnet 5.5 | $0.00023 | $0.00189 |
| Haiku 4.5 | $0.00012 | $0.00094 |
Grade A, and why
youtube-competitor-analyzer 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YouTube Competitor Analyzer
Find and analyze competitor channels using YouTube Data API v3.
Setup
- API Key: Get from Google Cloud Console - enable YouTube Data API v3
- Input: User's channel (for context) OR list of competitor channels to analyze directly
API Endpoints
BASE_URL = https://www.googleapis.com/youtube/v3
# Search channels
GET /search?part=snippet&q={query}&type=channel&maxResults={n}&key={API_KEY}
# Channel details
GET /channels?part=snippet,statistics,contentDetails,brandingSettings&id={ids}&key={API_KEY}
# Channel videos
GET /search?part=snippet&channelId={id}&order=date&type=video&maxResults=50&key={API_KEY}
# Video details
GET /videos?part=snippet,statistics,contentDetails&id={ids}&key={API_KEY}
Competitor Discovery Methods
1. Keyword Search
Extract keywords from user's channel (description, title, brandingSettings.keywords), search for channels:
GET /search?q={keyword}&type=channel&maxResults=10
2. Content Similarity
Get user's recent video titles, extract frequent words (>4 chars), search channels with those terms.
3. Category Search
Search within same YouTube category as user's channel.
4. Related Discovery
Search using user's video titles/descriptions to find channels creating similar content.
5. Direct Input
User provides specific channels to analyze: @handles, channel IDs, or URLs.
Competitor Ranking
// Size similarity (log scale)
sizeSimilarity = 1 - Math.abs(Math.log10(compSubs+1) - Math.log10(targetSubs+1)) / 10;
// Engagement per video
engagementRate = viewCount / (videoCount || 1);
// Overall score
overallScore = sizeSimilarity * 0.3 + relevanceScore * 0.7;
Sort by overallScore, return top 10-15.
Comparative Analysis
For each competitor, extract:
| Metric | Description |
|---|---|
| Subscribers | Direct count |
| Total Views | Channel lifetime views |
| Video Count | Total videos published |
| Views/Video | Average performance |
| Upload Frequency | Videos per month |
| Channel Age | Days since creation |
What ships with it
1 file 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.
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 · 139 lines · 117 tokens per session scan A 219f6f491f92
youtube-competitor-analyzer is a skill published in the GitHub repository nikhilbhansali/claude-youtube-skills (5 stars, last pushed 9mo ago), licensed MIT. It adds 117 tokens to every session and 944 once invoked, about $0.0005 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
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.
rudder-instrumentation-planning
Designs event taxonomies and instrumentation strategies from business requirements. Use when designing event taxonomy from scratch or restructuring existing instrumentation strategy.
rudder-instrumentation-debugging
Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.
rudder-ai-events-verify
Verifies RudderStack AI events locally and checks a move from existing RudderStack events: validates captures against the v0.3 schema, joins, switches and legacy events. Use when testing AI events, comparing old and new tracking, or when AI or MCP events look wrong or missing.