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/martindelophy/ai-video-editor/develop-timeline-studio-pluginnpx skills add MartinDelophy/ai-video-editor --skill develop-timeline-studio-plugingit clone --depth 1 https://github.com/MartinDelophy/ai-video-editorWrote 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/martindelophy/ai-video-editor/develop-timeline-studio-plugin)<a href="https://agentmods.dev/skills/martindelophy/ai-video-editor/develop-timeline-studio-plugin"><img src="https://agentmods.dev/badge/skills/martindelophy/ai-video-editor/develop-timeline-studio-plugin.svg" alt="Measured on agentmods" 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 | $0.00071 | $0.00736 |
| Opus 5 | $0.00036 | $0.00368 |
| Sonnet 5 | $0.00014 | $0.00147 |
| Haiku 4.5 | $0.00007 | $0.00074 |
Grade A, and why
develop-timeline-studio-plugin 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 yesterday.
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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop Timeline Studio generation plugins
Build a source-integrated generation connector that remains isolated from Timeline Studio's editing core and returns real downloadable media to My assets.
Start with the contract
Read ../../docs/generation-plugin-development.md completely before designing or changing a connector. Treat it as the source of truth for provider eligibility, runtime classes, manifest and adapter shapes, security, localization, output normalization, and completion criteria.
Also read the repository's AGENTS.md and inspect the current implementations in:
src/components/GenerationPlugins.jsxsrc/hooks/useGenerationPlugins.js
Do not assume that an external installable plugin runtime already exists. Current plugins are reviewed source integrations. If the shared registry and host described by the contract are absent, make only the bounded extraction required for the requested provider and preserve existing provider behavior.
Decide before implementing
Use the provider's current official documentation to establish:
- a stable task/result API or owned browser SDK;
- automatic retrieval of every generated image or video;
- authentication and credential ownership;
- browser and CORS requirements;
- real job, progress, error, and cancellation semantics;
- temporary-output lifetime, cost, region, and account constraints.
Reject a generic embed or manual result-URL workflow. Stop when the provider requires a developer secret in browser code or lacks a safe automatic output route. State the exact missing capability rather than simulating it.
Preserve the host boundary
- Put provider transport and response parsing in an isolated adapter.
- Register identity and capabilities through one declarative manifest.
- Let the host own concurrency, cancellation arbitration, media validation, object URLs, notifications, and My assets commits.
- Never let a provider mutate the timeline or receive broad editor state.
- Download and decode output bytes before reporting completion.
- Import all declared outputs, not only the first.
- Use provider-backed progress or an indeterminate state; never fabricate percentages.
- Keep authentication, connection, running, cancelled, complete, and error states honest.
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.
- yesterday First seen · 60 lines · 71 tokens per session scan A 3913554b6401
develop-timeline-studio-plugin is a skill published in the GitHub repository MartinDelophy/ai-video-editor (768 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 736 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
PR Review
Guidelines and tools for reviewing pull requests in the Angular repository.
adev-writing-guide
Comprehensive writing guide for Angular documentation (adev). Covers Google Technical Writing standards, Angular-specific markdown extensions, code blocks, and components. You MUST use this skill any time you plan to create, edit, or review documentation files in adev/ or adev/src/content.
reference-signal-forms
Explains the mental model and architecture of the code under packages/forms/signals. You MUST use this skill any time you plan to work with code in packages/forms/signals.
angular-developer
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component…
reference-compiler-cli
Explains the mental model and architecture of the code under packages/compiler-cli. You MUST use this skill any time you plan to work with code in packages/compiler-cli.
reference-core
Explains the mental model and architecture of the code under packages/core. You MUST use this skill any time you plan to work with code in packages/core.