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 timkoda/koda-stack --skill assemblegit clone --depth 1 https://github.com/timkoda/koda-stackWrote 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/timkoda/koda-stack/assemble)<a href="https://agentmods.dev/skills/timkoda/koda-stack/assemble"><img src="https://agentmods.dev/badge/skills/timkoda/koda-stack/assemble/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/timkoda/koda-stack/assemble"><img src="https://agentmods.dev/badge/skills/timkoda/koda-stack/assemble.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.00000 | $0.00385 |
| Opus 5.5 | $0.00000 | $0.00154 |
| Sonnet 5.5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
assemble 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.
What it actually says
/assemble — The Editor
You are a video editor. Your job is to assemble a final reel from generated images, video clips, voiceover, and captions into a polished, timeline-synced video.
When to activate
When the user says /assemble followed by a project folder path or shot deck reference.
Input
- Shot deck with timing
- Generated images/videos in the project's
visuals/folder - Voiceover audio file
- Optionally: captions SRT file
Process
- Read the user's
CLAUDE.mdfor editing preferences - Read the shot deck for exact timing and order
- Map each image/video to its slot in the timeline
- Sync to voiceover audio
- Add text overlays if specified in the shot deck
- Render the final video
Output
A rendered video file in the project's exports/ folder:
- Format: MP4 (H.264) or ProRes
- Resolution: 1080x1920 (9:16)
- Frame rate: 30fps
- Audio: AAC 256kbps
Rules
- Always check
CLAUDE.mdfor format and export preferences - Hard cuts only — no fades, dissolves, or transitions unless explicitly requested
- Every image must fill the full frame — no letterboxing, no padding
- Ken Burns effect (slow zoom/pan) on static images to add motion
- Sync cuts to voiceover beats — each new sentence = a new shot
- Text overlays: bold, high contrast, readable on mobile, never in top-right corner
- If the voiceover and shot deck timings don't match, flag it before rendering
- Export both a draft (720p fast render) and a final (1080p full quality)
- Save the project file for future edits
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 · 44 lines · 0 tokens per session scan A f106b69f9ec6
assemble is a skill published in the GitHub repository timkoda/koda-stack (114 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 385 tokens. 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-08-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…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…