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 tough-tongue/demo-prep-skills --skill demo-reviewgit clone --depth 1 https://github.com/tough-tongue/demo-prep-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/tough-tongue/demo-prep-skills/demo-review)<a href="https://agentmods.dev/skills/tough-tongue/demo-prep-skills/demo-review"><img src="https://agentmods.dev/badge/skills/tough-tongue/demo-prep-skills/demo-review/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/tough-tongue/demo-prep-skills/demo-review"><img src="https://agentmods.dev/badge/skills/tough-tongue/demo-prep-skills/demo-review.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.00048 | $0.01636 |
| Opus 5 | $0.00024 | $0.00818 |
| Sonnet 5 | $0.00010 | $0.00327 |
| Haiku 4.5 | $0.00005 | $0.00164 |
Grade A, and why
demo-review 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 12d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Demo Review
Analyze a product demo — either a recorded video or a website's "Book a Demo" experience — and produce a structured quality report with scores, strengths, opportunities, and actionable improvements.
When to Use
- User says "review this demo: [URL]"
- User wants to audit their own recorded demo for improvement
- User wants to analyze a competitor's or prospect's demo experience
- User wants to create a value-first outreach asset (audit report to send to a prospect)
Required Inputs
Source: [One of the following]
- Video URL (Loom, YouTube, Vimeo)
- Website URL (to audit their "Book a Demo" flow)
- Video file path (local recording)
Purpose: [Self-improvement / Competitor analysis / Prospect outreach]
If the source is a website URL, navigate to the site and evaluate the entire demo experience — from the first CTA to what happens after you request a demo.
Process
Step 1: Understand the Context
If reviewing a prospect's or competitor's demo:
- Navigate to their website
- Understand what they sell and who they sell to
- Note the demo CTA (Book a Demo? Watch Demo? Free Trial?)
- Follow the flow as a prospect would
If reviewing the user's own demo:
- Read
company-profile.mdfor product context - Understand what the demo is supposed to accomplish
Step 2: Evaluate Against Criteria
A. Structure and Pacing
| What to Observe | Why It Matters | Rating Notes |
|---|---|---|
| How long before they show the product? | Long intros lose people | Under 30s is good, over 2 min is problematic |
| Total demo length | Too long = drop-off | 3-7 min ideal for recorded, 20-30 min for live |
| Logical flow or jumping around? | Confusion kills conversion | Should follow a natural user journey |
| Clear "aha moment"? When? | Should hit early | Note the timestamp |
B. Messaging and Clarity
| What to Observe | Why It Matters | Rating Notes |
|---|---|---|
| Do they explain the problem first? | Context before solution | Problem → Solution → How |
| Is the value prop clear in 30 seconds? | Attention is short | Should know what it does immediately |
| Jargon or insider language? | Alienates new prospects | Flag specific terms |
| Do they address objections? | Unaddressed concerns fester | Note which ones are covered |
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.
- 12d ago First seen · 182 lines · 48 tokens per session scan A c20e78af15de
demo-review is a skill published in the GitHub repository tough-tongue/demo-prep-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 48 tokens to every session and 1,636 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…