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 renalpelvisdeinocheirus70/ozor-skills --skill ozor-changelog-to-videogit clone --depth 1 https://github.com/renalpelvisdeinocheirus70/ozor-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/renalpelvisdeinocheirus70/ozor-skills/ozor-changelog-to-video)<a href="https://agentmods.dev/skills/renalpelvisdeinocheirus70/ozor-skills/ozor-changelog-to-video"><img src="https://agentmods.dev/badge/skills/renalpelvisdeinocheirus70/ozor-skills/ozor-changelog-to-video/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/renalpelvisdeinocheirus70/ozor-skills/ozor-changelog-to-video"><img src="https://agentmods.dev/badge/skills/renalpelvisdeinocheirus70/ozor-skills/ozor-changelog-to-video.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.00130 | $0.01992 |
| Opus 5 | $0.00065 | $0.00996 |
| Sonnet 5 | $0.00026 | $0.00398 |
| Haiku 4.5 | $0.00013 | $0.00199 |
Grade A, and why
ozor-changelog-to-video 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.
This is a copy
100% identical to ozor-changelog-to-video — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ozor Changelog-to-Video Converter
Transform changelogs, release notes, and version updates into polished, ready-to-paste Ozor.ai video prompts. This skill reads structured change lists and produces scene-by-scene video prompts that announce updates in a visually compelling way.
Supported Input Types
- CHANGELOG.md — standard Keep a Changelog format
- GitHub Releases — release descriptions with tags
- Release notes — bullet-pointed feature lists
- Version summaries — "What's New" style documents
- Commit summaries — grouped commit messages for a release
- Jira/Linear release notes — exported issue lists
Workflow
Phase 1 — Parse the Changelog
Read the changelog and extract:
- Version number — the release tag (e.g., v2.4.0)
- Release date — when it shipped
- Change categories — group changes by type:
- New features — entirely new capabilities
- Improvements — enhancements to existing features
- Bug fixes — resolved issues
- Breaking changes — anything that requires user action
- Deprecations — features being phased out
- Headline change — the single most impactful or user-requested change
- Change count — total number of changes (used for duration estimation)
Phase 2 — Prioritize for Video
Not every changelog entry deserves a scene. Apply these rules:
Always include:
- The headline feature (biggest or most requested change)
- Any new feature that changes the user's workflow
- Breaking changes (users need to know)
Include if space allows:
- Significant improvements (performance, UX)
- Highly requested bug fixes
Skip for video (mention in notes):
- Minor bug fixes
- Internal refactors
- Dependency updates
- Documentation changes
Scene budget by change count (target ~1 scene per 3 seconds of video):
- 1–3 changes: 6–8 scenes (intro + 2–3 per change + summary + CTA)
- 4–7 changes: 10–15 scenes (intro + 2–3 per top change + summary + CTA)
- 8+ changes: 15–20 scenes (intro + 2–3 per top change + "and more" + CTA)
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 · 174 lines · 130 tokens per session scan A ac6145340d09
ozor-changelog-to-video is a skill published in the GitHub repository renalpelvisdeinocheirus70/ozor-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 130 tokens to every session and 1,992 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ozor-changelog-to-video, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ozor-prompt-optimizer
Analyze and improve existing Ozor.ai video prompts for better output quality. Use this skill whenever the user has an Ozor prompt that produced mediocre results, wants to improve a video prompt, needs help debugging why a video didn't turn out well, or wants expert feedback on their prompt before running it. Trigger…
ozor-video-best-practices
Expert guide for crafting high-quality video prompts for Ozor.ai, the AI video generation platform. Use this skill whenever the user mentions Ozor, wants to create a launch video, product demo, feature announcement, explainer video, social ad, release notes video, investor update, tutorial, or any marketing video.…
ozor-doc-to-video
Convert any document into a production-ready Ozor.ai video prompt. Use this skill whenever the user uploads a document (PDF, PowerPoint, Google Doc, Markdown, text file, or URL) and wants to turn it into a video. Also trigger when the user mentions 'turn this doc into a video', 'make a video from this PDF', 'video…
ozor-landing-page-to-video
Convert any landing page or website into an Ozor.ai video prompt. Use this skill whenever the user provides a URL, landing page content, or website copy and wants to turn it into a video. Trigger on phrases like 'make a video from my website', 'video from this landing page', 'turn my homepage into a video', 'video…
ozor-changelog-to-video
Convert changelogs, release notes, and version updates into Ozor.ai video prompts. Use this skill whenever the user has a CHANGELOG.md, release notes, GitHub release, version bump summary, or any list of product changes and wants to turn them into a video. Trigger on phrases like 'video from my changelog', 'release…
ozor-document-video
Turn a real document (PDF, PPTX, DOCX, Keynote export, slide deck, proposal, whitepaper, report) into a finished AI-generated video using the Ozor MCP. Use this skill whenever the user attaches, uploads, references, or points to a document file and wants a video from it — e.g. 'make a video from this pitch deck'…