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 buildfastwithai/gen-ai-experiments --skill demo-site-buildergit clone --depth 1 https://github.com/buildfastwithai/gen-ai-experimentsWrote 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/buildfastwithai/gen-ai-experiments/demo-site-builder)<a href="https://agentmods.dev/skills/buildfastwithai/gen-ai-experiments/demo-site-builder"><img src="https://agentmods.dev/badge/skills/buildfastwithai/gen-ai-experiments/demo-site-builder/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/buildfastwithai/gen-ai-experiments/demo-site-builder"><img src="https://agentmods.dev/badge/skills/buildfastwithai/gen-ai-experiments/demo-site-builder.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.00071 | $0.01183 |
| Opus 5.5 | $0.00028 | $0.00473 |
| Sonnet 5.5 | $0.00014 | $0.00237 |
| Haiku 4.5 | $0.00007 | $0.00118 |
Grade A, and why
demo-site-builder 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Demo Site Builder
Turn a repository analysis into ONE self-contained demo.html that a reader can open in any browser and immediately understand what the project does and why it matters. The page both explains and, where feasible, demonstrates the functionality.
Non-negotiables
- Single file. Everything — HTML, CSS, JS — lives in one
demo.html. No build step, nonode_modules, no local asset files. - Works offline by double-click. It must render fully when opened directly from disk (
file://). Only optional enhancements (a web font, a syntax-highlight CDN, an icon set) may load from a CDN, and the page must still look correct if those fail. - Grounded in the analysis. Every feature, number, code sample, and claim comes from the
analyze_repooutput (description, README, languages, topics, stars, commits). Never invent capabilities, benchmarks, or quotes. If the README shows a real usage snippet, reuse it verbatim. - No secrets, no live network calls to the user's services. A demo may simulate behavior in-browser, but must not require API keys or hit private endpoints.
Page structure (in order)
- Hero — project name, a one-line tagline distilled from the description, 2-4 badges (language, license, stars, latest version if any), and two buttons: "View on GitHub" (links to the repo URL) and a "See it in action" anchor to the demo section.
- Problem → Solution — 1-2 short paragraphs: the problem the repo solves and how it solves it. Pulled from the README intro.
- Key features — a responsive grid of 3-6 cards, each with an icon/emoji, a title, and one sentence. Only features evidenced by the analysis.
- Live demo or walkthrough — the centerpiece:
- If the repo is a browser-runnable JS/TS library or produces visual/text output that can be reproduced client-side, embed a genuinely interactive widget (inputs → live result) implemented in inline JS.
- If it is a CLI, backend, or non-browser tool, build a realistic simulated terminal / API playground: the user clicks example commands and sees representative output (clearly labelled "sample output"), driven by canned data taken from the README. Do not fake success of things you cannot actually run.
- Always label simulated output honestly.
- Usage / code example — the real install + minimal usage from the README, in a styled, copy-to-clipboard code block.
- Tech stack — languages (with the analyzed percentages) and notable topics as pills.
- Footer — repo link, license, "Generated launch demo" note, contributor credit.
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.
- 1mo ago First seen · 62 lines · 71 tokens per session scan A 4d651499cc9c
demo-site-builder is a skill published in the GitHub repository buildfastwithai/gen-ai-experiments (789 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,183 once invoked, about $0.0003 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-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…
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…