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 dkadts/landing-kit-building --skill mediagit clone --depth 1 https://github.com/dkadts/landing-kit-buildingWrote 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/dkadts/landing-kit-building/media)<a href="https://agentmods.dev/skills/dkadts/landing-kit-building/media"><img src="https://agentmods.dev/badge/skills/dkadts/landing-kit-building/media/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/dkadts/landing-kit-building/media"><img src="https://agentmods.dev/badge/skills/dkadts/landing-kit-building/media.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.00042 | $0.01341 |
| Opus 5 | $0.00021 | $0.00671 |
| Sonnet 5 | $0.00008 | $0.00268 |
| Haiku 4.5 | $0.00004 | $0.00134 |
Grade A, and why
media 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 9d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/media
Solves the assets-optimization bottleneck (usually done twice in a naive workflow).
When to use
- After
/inbox(materials validated). - Every time a new batch of media arrives.
Requirements
- Tools available:
ffmpeg(for video + posters),cwebp/avifenc/sharp(for photos). - On Windows the simplest path: node.js +
sharp(npm install -g sharp-cli) +ffmpeg. - If tools are missing — inform the user, provide install commands.
Process
Step 1. Read config
brief/00-priority.md— desktop-first or mobile-first (affects priority sizes).brief/06-technical.md— media hosting decision (local / Vercel / R2).brief/blocks/video-embed.md— hero-loop needed? formats?
Step 2. Walk inbox/media/photos/
For each photo:
A. Determine purpose
- From filename /
brief/04-content.md. - Hero — priority, LCP-critical.
- Portrait / case — standard.
- Icon-size (small) — optimize differently.
B. Generate size variants
For desktop-first:
- 480w, 768w, 1200w, 1920w, 2400w.
For mobile-first:
- 320w, 480w, 768w, 1200w, 1920w.
C. Convert to formats
.webp(required, quality ~80-85)..avif(optional, quality ~60-70 — better compression).- Original
.jpgfallback — only if old-browser support needed (usually not).
D. Save in site/media/
Naming: <name>-<width>.webp
Example:
site/media/
├── hero-480.webp
├── hero-768.webp
├── hero-1200.webp
├── hero-1920.webp
└── hero-2400.webp
E. Generate srcset-snippet for this file
Save to site/media/_srcset-snippets.md for use in /build:
<img src="/media/hero-1200.webp"
srcset="/media/hero-480.webp 480w,
/media/hero-768.webp 768w,
/media/hero-1200.webp 1200w,
/media/hero-1920.webp 1920w,
/media/hero-2400.webp 2400w"
sizes="(max-width: 768px) 100vw, 60vw"
alt="TBD"
loading="lazy" decoding="async">
Step 3. Walk inbox/media/videos/
For each video:
A. Format
.webm(VP9, main) — required..mp4(H.264, fallback) — required.
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.
- 9d ago First seen · 166 lines · 42 tokens per session scan A 275b5d49f9b3
media is a skill published in the GitHub repository dkadts/landing-kit-building (2 stars, last pushed 20d ago), licensed MIT. It adds 42 tokens to every session and 1,341 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
p5js
Use when users request: p5.js sketches, creative coding, generative art, interactive visualizations, canvas animations, browser-based visual art, data viz, shader effects, or any p5.js project.
design
Use when the user wants the visual/experiential design of a product done systematically — a design system, a screen, a landing page, or a visual identity — grounded in researched real-world prior art and free of AI slop. Establishes/extends the design system, invokes the matching local taste skill, dispatches the…
remotion
Render a short (10s) video on any topic with Remotion - the agent writes a storyboard JSON, a bundled React/Remotion project renders it to an MP4, and the clip is committed to the repo and delivered by URL. No editor, no external generative API.
animate
Generate animated videos and motion graphics from natural language descriptions. Creates a standalone Vite + React project with Framer Motion scenes that auto-play in the browser. Use when the user wants to create animations, motion graphics, video intros, animated presentations, or product demos.
next-upgrade
Upgrade Next.js to the latest version following official migration guides and codemods.
regenerate-api
Regenerate the AppointMe frontend API client (orval/TanStack Query hooks + TypeScript schemas) after the backend OpenAPI surface changes. Use this whenever backend endpoints, request/response DTOs, or other contract-affecting types are added, removed, or modified — e.g. after editing files under src/AppointMe.Api…