Borrowing it
Nothing to install: this file belongs to emilyLi2020/WAVE. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/emilyLi2020/WAVE/main/.agents/skills/demo-prep/SKILL.mdgit clone --depth 1 https://github.com/emilyLi2020/WAVEWrote 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/emilyli2020/wave/demo-prep)<a href="https://agentmods.dev/skills/emilyli2020/wave/demo-prep"><img src="https://agentmods.dev/badge/skills/emilyli2020/wave/demo-prep/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/emilyli2020/wave/demo-prep"><img src="https://agentmods.dev/badge/skills/emilyli2020/wave/demo-prep.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.00045 | $0.00531 |
| Opus 5.5 | $0.00018 | $0.00212 |
| Sonnet 5.5 | $0.00009 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
demo-prep 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
Demo Prep
The user is about to present their project at a hackathon or demo day. Help them create a polished, timed demo script that tells a compelling story.
Step 1: Gather Context
Ask the user:
- What does your app do? (one sentence)
- Who is it for?
- What is the single most impressive thing it does?
- How long is your presentation slot? (default: 3 minutes)
- Will you do a live demo, recorded video, or slides?
Step 2: Write the Demo Script
Structure the script in three acts:
Act 1: The Problem (30 seconds)
- One sentence describing the pain point
- One concrete example or statistic that makes it real
- "What if there was a better way?"
Act 2: The Solution (90 seconds)
- Show the app running (live or recorded)
- Walk through the core user flow step by step
- Highlight the "wow moment" (the single most impressive feature)
- Keep clicks to a minimum; narrate what is happening
Act 3: The Impact (30 seconds)
- What changes because this exists?
- One metric, testimonial, or future vision
- Clear closing statement
Step 3: Prepare the Backup Plan
- Record a screen capture of the full demo flow (in case live demo fails)
- Prepare 2-3 screenshots of key screens as fallback slides
- Test the app on the presentation machine/network before going on stage
- Have the live URL ready as a backup to localhost
Step 4: Rehearse Checklist
- Timed the full presentation (fits within the slot)
- Practiced at least 3 times out loud
- Tested the app on the demo machine
- Backup video/screenshots are ready
- Opening line is memorized (no fumbling the start)
- Closing line is memorized (end strong)
Output
Return:
- Script: The full narrated demo script with timestamps
- Click Path: Exact sequence of actions to perform during the demo
- Backup Plan: What to do if the live demo breaks
- Q&A Prep: 3-5 likely questions judges will ask, with suggested answers
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 · 62 lines · 45 tokens per session scan A 9aa4c220902e
demo-prep is a skill published in the GitHub repository emilyLi2020/WAVE (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 531 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-08-31.
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…
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…
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.