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 develop-topicgit 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/develop-topic)<a href="https://agentmods.dev/skills/sugarforever/boring-video-studio/develop-topic"><img src="https://agentmods.dev/badge/skills/sugarforever/boring-video-studio/develop-topic/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/develop-topic"><img src="https://agentmods.dev/badge/skills/sugarforever/boring-video-studio/develop-topic.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.00039 | $0.00937 |
| Opus 5.5 | $0.00016 | $0.00375 |
| Sonnet 5.5 | $0.00008 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
develop-topic 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop topic
Turn a candidate topic into an approved content contract. The work is ready for writing only when the argument, evidence, and boundaries no longer need to be invented downstream.
Scope
Start from one candidate topic or a small, naturally bounded set. When several nearby directions remain, compare them lightly for audience value, novelty, verifiability, demonstrability, author fit, and overclaiming risk; ask the user to choose before deep research. Open-ended trend scanning and maintaining an idea backlog stay outside this skill.
Evidence workspace
Create a content/ directory in the video project:
content/
|-- RESEARCH.md
|-- TOPIC.md
`-- experiments/
Use RESEARCH.md for sourced facts, interpretations, disagreements, unknowns, rejected directions, and links to primary material. Keep collection separate from editorial selection.
Treat a claim as material when it affects whether the subject works, matters to the audience, differs from an alternative, can be demonstrated, or remains valid within the stated scope. Support it with a source or experiment strong enough for that exact claim; label weaker evidence provisional rather than silently stretching it.
When a claim needs runnable evidence, perform the smallest experiment that can settle it and write content/experiments/<name>.md with the question, method, samples, environment, command, results, limitations, and conclusions the result supports. Keep code and raw data in the project that owns them; record their paths and Git revision instead of copying them into the video project.
Content contract
Write content/TOPIC.md:
---
status: draft
audience: ...
core_question: ...
thesis: ...
scope: ...
voice:
language: ...
skills: []
documents: []
unavailable: []
status: resolved | assumed
---
# Working title
## Reader promise
## Argument
### A01 - Claim
- role: Why this claim exists in the argument
- claim: The exact proposition
- evidence: Links to RESEARCH.md headings or experiment reports
- confidence: established | provisional
- boundary: What the evidence does not establish
## Out of scope
## Open questions
## Alternate titles
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 0403125cae35
- 13d ago Changed · +2 lines d96c35ca4335
- 18d ago First seen · 91 lines · 39 tokens per session scan A b509f664209f
develop-topic is a skill published in the GitHub repository sugarforever/boring-video-studio (184 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 937 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-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.