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/cdeistopened/skill-stack/video-caption-creationnpx skills add cdeistopened/skill-stack --skill video-caption-creationgit clone --depth 1 https://github.com/cdeistopened/skill-stackWhat 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.00036 | $0.02813 |
| Opus 5 | $0.00018 | $0.01406 |
| Sonnet 5 | $0.00007 | $0.00563 |
| Haiku 4.5 | $0.00004 | $0.00281 |
Grade A, and why
video-caption-creation 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 2d 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 — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Video Caption Writer
Purpose
This skill creates algorithm-optimized captions and on-screen text for short-form video content using the "Triple Word Score" system to maximize reach and engagement.
Core Philosophy: Content serves the topic first. When you serve the topic correctly, algorithms will serve your content to people interested in that topic.
When to Use This Skill
Use this skill when you need to:
- Create on-screen text hooks for video clips (3-5 options per clip)
- Write captions for short-form video (TikTok, Instagram, YouTube Shorts, etc.)
- Optimize video for algorithm discovery (topic identification in first 10 seconds)
- Generate strategic hashtag sets (10-12, broad to specific)
Do NOT use for:
- Text-only social posts (use
social-content-creationskill instead) - Long-form YouTube videos (separate workflow)
- Podcast show notes (separate podcast workflow)
The Triple Word Score System
Algorithms and humans need to immediately understand your content through FOUR signals:
1. Audio Transcript (MOST IMPORTANT)
- What you say out loud - algorithms auto-transcribe this
- Explicitly say topic words in first 10 seconds
- Repeat core terminology throughout
- Use natural speech patterns with topic-relevant vocabulary
2. On-Screen Text Reinforcement
- Visual overlay that reinforces spoken words
- Lead with topic words in first text overlay
- Use bold, clear terminology
- Don't compete with audio - reinforce it
3. Caption Copy Optimization
- Post description with topic-relevant keywords
- Open with topic-relevant phrases in first sentence
- Include natural keyword variations
- Provide context for algorithm understanding
4. Strategic Hashtag System
- 10-12 hashtags (optimal range)
- Mix broad and specific (#Productivity + #TimeManagement)
- Include audience-specific (#Entrepreneurs)
- Span from general to niche
When all four signals align, algorithms AND humans immediately recognize: "This is for me."
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.
- 2d ago First seen · 421 lines · 36 tokens per session scan A 027cbcd31147
video-caption-creation is a skill published in the GitHub repository cdeistopened/skill-stack (27 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 2,813 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…