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 calesthio/generative-media-skills --skill screen-demo-productiongit clone --depth 1 https://github.com/calesthio/generative-media-skillsWrote 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/calesthio/generative-media-skills/screen-demo-production)<a href="https://agentmods.dev/skills/calesthio/generative-media-skills/screen-demo-production"><img src="https://agentmods.dev/badge/skills/calesthio/generative-media-skills/screen-demo-production/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/calesthio/generative-media-skills/screen-demo-production"><img src="https://agentmods.dev/badge/skills/calesthio/generative-media-skills/screen-demo-production.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00077 | $0.02764 |
| Opus 5 | $0.00039 | $0.01382 |
| Sonnet 5 | $0.00015 | $0.00553 |
| Haiku 4.5 | $0.00008 | $0.00276 |
Grade A, and why
screen-demo-production 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 13d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Screen demo production
Use this skill when the central evidence is an interface being operated over time: commands run, files change, controls activate, application state changes, or a workflow completes.
This is broader than SaaS marketing. It covers instructional, support, onboarding, engineering, release-note, internal-training, terminal, IDE, browser, desktop, remote-desktop, and multi-application demonstrations.
Evidence stance
- Documented fact: behavior from official capture/automation, accessibility, privacy, or security sources.
- Production heuristic: a practical direction choice to test with the audience and final raster.
- Empirical observation: a result verified in the actual product/build, rehearsal, capture, or render.
Tool and OS behavior is volatile. Facts were verified 2026-07-12. Record product/build, browser/OS, automation/capture versions, fixtures, mocks, and permissions.
Classify the truth claim
Every demo must declare one:
- Authentic capture: pixels come from the stated product or OS during an actual run.
- Controlled authentic capture: the real UI runs with seeded data, fixed time, mocked dependencies, automation, or other material controls. Disclose them.
- Illustrative synthetic: terminal or UI is recreated for explanation or pacing. Never describe it as a recording of a real run.
- Hybrid: authentic pixels combined with synthetic cursor, typing, callouts, timing reconstruction, or other layers. Record each component.
Choose the least invasive mode that supports the intended claim. Synthetic UI is appropriate for conceptual or privacy-sensitive explanation; browser automation for repeatable real web flows; OS/window capture when native chrome, terminal/IDE behavior, permissions, or cross-app interaction matters.
Do not present simulated data or mocked services as proof of live performance, security, a transaction, benchmark, or customer outcome.
Boundaries
This skill owns capture-mode choice, workflow scripting, reset, privacy review, readability, cursor/callout direction, narration/caption synchronization, aspect variants, retakes, QA, and provenance.
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.
- 13d ago First seen · 232 lines · 77 tokens per session scan A d9bdde83a601
screen-demo-production is a skill published in the GitHub repository calesthio/generative-media-skills (170 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 2,764 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-08-30.
Other skills, from other repositories
computer-use
Read and drive native desktop applications through the accessibility layer — list on-screen apps, snapshot one window as a numbered element tree, then click / type / set a value / scroll / drag / run a named action, by element index or by screen coordinates. Use for work in a desktop app rather than a web page. Full…
feature-demo-recording
Record a demo video of a web feature from a real browser. Two modes -- a NARRATED film where measured voiceover drives the timeline (designed slides, subtitles, punch-in camera, rendered from an HTML timeline), and a SILENT evidence clip for a PR or a QA pass. Use when the user asks to record a video, demo, or screen…
browser-recording
Record a browser flow as a video/GIF for evidence — animations, transitions, and multi-step interactions that a still screenshot cannot prove. Drives the project's own Playwright through a bundled runner, then converts to mp4 + GIF via ffmpeg. Use when the user asks to record a demo, capture a GIF or video of the UI…
web-browse
Open a REAL external web page so the user can see it in Kiro Crew's Browser panel. PRIMARY path is the browser MCP tool (drives the built-in native panel); playwright-cli is the fallback for remote/plain-browser sessions and for attached logged-in browsers. Use when the user wants to VIEW / verify / "show me" an…
web-verify
Look at your OWN front-end change before claiming it works -- navigate the loopback URL of a dev server or pod you started, screenshot the surface you changed, read the image to judge it, and embed it in chat. Three capture backends: playwright-cli (the session the dashboard Browser panel shows), the agent-browser CLI…
browser-auth
Browse sites that need a logged-in session with playwright-cli, using attach mode, saved storage state, or individual cookies. Use when a page is behind a login wall and a plain open lands on a sign-in screen.