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 jykim/claude-obsidian-skills --skill create-vlog-scriptgit clone --depth 1 https://github.com/jykim/claude-obsidian-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/jykim/claude-obsidian-skills/create-vlog-script)<a href="https://agentmods.dev/skills/jykim/claude-obsidian-skills/create-vlog-script"><img src="https://agentmods.dev/badge/skills/jykim/claude-obsidian-skills/create-vlog-script/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/jykim/claude-obsidian-skills/create-vlog-script"><img src="https://agentmods.dev/badge/skills/jykim/claude-obsidian-skills/create-vlog-script.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.00056 | $0.00682 |
| Opus 5.5 | $0.00022 | $0.00273 |
| Sonnet 5.5 | $0.00011 | $0.00136 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
create-vlog-script 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Vlog Script
Turn spoken ideas and available footage into a coherent, recordable story.
Start with the story
- Transcribe and lightly polish voice notes without erasing the speaker's point of view.
- Establish a clear progression: lived memory or question, change or tension, concrete experience, reflection, and a personal resolution.
- Make transitions part of the narration on the following scene's slide. Do not isolate them into separate transition slides unless the user explicitly asks for title cards.
- Prefer one specific event or image over general claims. Let a personal observation lead into broader context rather than the reverse.
Work from actual assets
- Inventory the supplied media folder and visually inspect representative frames before assigning a clip to narration. Do not infer a clip's subject from its filename.
- Rename original files only when the user asks, using concise, truthful, chronological names. Never label an ambiguous clip as a specific event or person without visual confirmation.
- Use real supplied photos, video previews, and article captures in a recording guide wherever possible. Use a clearly labeled placeholder only when an asset has not been supplied or cannot be used yet.
- Distinguish actual footage, screenshots, recreated graphics, and AI-generated concept images in both captions and narration. Never present a concept image as real data or documentary footage.
- For browser-unfriendly source media, use a verified preview or still in the guide and retain the original as the final editing source.
Create a recording-slide guide
When the user wants to record narration, deliver an HTML slide guide rather than a document-only outline.
- Give each slide the likely final-video composition: a full-screen background or a clear media panel, narration large enough to read aloud, and a small on-screen editing cue.
- Support forward/back navigation by keyboard, click, and a visible slide counter. Include a full-screen shortcut.
- Put the full spoken text—including connective phrases—on the slide. The user should not need a separate script while recording.
- Place visual prompts near their corresponding narration: exact supplied asset, intended crop or hold, source article link, or an explicit placeholder.
- Keep the guide presentation-oriented: do not overload it with production notes that do not affect recording.
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.
- 1mo ago First seen · 49 lines · 56 tokens per session scan A 62b9f1cfcdb3
create-vlog-script is a skill published in the GitHub repository jykim/claude-obsidian-skills (50 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 682 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-09-22.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…