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 sugarforever/boring-video-studio --skill to-articlegit clone --depth 1 https://github.com/sugarforever/boring-video-studioWrote 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/sugarforever/boring-video-studio/to-article)<a href="https://agentmods.dev/skills/sugarforever/boring-video-studio/to-article"><img src="https://agentmods.dev/badge/skills/sugarforever/boring-video-studio/to-article/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/sugarforever/boring-video-studio/to-article"><img src="https://agentmods.dev/badge/skills/sugarforever/boring-video-studio/to-article.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.00031 | $0.00851 |
| Opus 5.5 | $0.00012 | $0.00340 |
| Sonnet 5.5 | $0.00006 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
to-article 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 4d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To article
Turn an approved content/TOPIC.md into content/ARTICLE.md: the readable content master for both the eventual blog post and the video plan.
Preconditions
Read content/TOPIC.md, content/RESEARCH.md, every cited experiment report, and the source material needed to verify the selected evidence. Continue only when TOPIC.md has status: approved.
Return to /develop-topic when writing exposes a missing material claim, contradictory evidence, an unsupported conclusion, or a needed change to the approved audience, thesis, scope, argument, evidence, or conclusion boundaries. Immediately return TOPIC.md to status: draft, resolve the gap there, and renew topic approval before drafting from it. Adding evidence that changes the confidence, boundary, or interpretation is material; adding an equivalent source without changing the contract is not.
Voice
Resolve the article voice from the approved topic. Before drafting, inspect the available skills for a writing-style skill matching the output language and content type, then load every applicable user, project, or brand style source named in voice.skills or voice.documents.
If no reliable source exists for a publication-grade article, ask one compact question for the desired voice or a sample. When the user delegates that choice, or the article is explicitly an internal draft, use a clear explanatory default and record voice.status: assumed. Record unavailable named sources under voice.unavailable; they are not evidence that their rules were applied. An unavailable source does not block drafting when another available source resolves the voice.
Draft
Write a complete, platform-independent article. It must stand alone for a reader, preserve the approved argument and boundaries, distinguish fact from interpretation, and cite the original sources behind material claims. Use headings, links, tables, or notes when they help reading; site-specific SEO fields, publishing components, and platform paths belong to a later publishing adaptation.
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.
- 4d ago Changed cfc8a6ef3656
- 13d ago Changed · +2 lines a439a4975f3d
- 18d ago First seen · 61 lines · 31 tokens per session scan A c24e7967a526
to-article is a skill published in the GitHub repository sugarforever/boring-video-studio (184 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 851 once invoked, about $0.0001 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-30.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.