What is review.create_demo?

A documentation tool that writes a short Markdown guide for running a software tool and checking what it produces.

Use it to create `code_demo.md` with run instructions, generated files, and notes from a past run.

It puts the command, requirements, outputs, and verification steps in one place so someone can try the tool quickly without guessing.

review.create_demo — Skill for Claude Code by gpsaggese/helpers

Install

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.

Any agent

npx skills add gpsaggese/helpers --skill review.create_demo

Clone the repo

git clone --depth 1 https://github.com/gpsaggese/helpers

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gpsaggese/helpers/review.create_demo/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/review.create_demo)

Your own site

<a href="https://agentmods.dev/skills/gpsaggese/helpers/review.create_demo"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/review.create_demo/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gpsaggese/helpers/review.create_demo"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/review.create_demo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,664 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.01664
Opus 5.5	$0.00000	$0.00666
Sonnet 5.5	$0.00000	$0.00333
Haiku 4.5	$0.00000	$0.00166

Measured yesterday against content hash dd7ad0bca861, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review.create_demo 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 yesterday.

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.

.claude/skills/review.create_demo/SKILL.md · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Goal

Given a dir that holds a tool, write code_demo.md in that dir
The file has four parts:
- What the tool does, in a few lines
- What to run: the command, its needs, its cost, and how long it takes
- What is generated: each output file, what it holds, and the stage that writes it
- What a past run gave, and how to check the output
Keep it short: a reader must run the demo after reading it for 5 mins
It is the source of the end-to-end demo in code_tour.md. The skill .claude/skills/review.create_code_tour/SKILL.md points to this file and does not repeat it

Conventions

Follow the template .claude/templates/review_create_demo.template.md
Follow .claude/skills/text.rules.md and .claude/skills/markdown.rules.md
Name each file in backticks, with its path from the repo root
Put each command in a fenced bash block, with > before the command
Take facts from the dir's README and from the files a run leaves. If a fact is not clear, write unknown and do not guess

Workflow

Get the Input

Take the dir from the arguments. If none is given, use the current dir
- If the dir does not exist, report the error and stop
Write code_demo.md in the dir. The name is fixed, so it does not follow ## Generated File Naming of .claude/skills/skill.rules.md
- If the file exists, read it, then overwrite it
Take the dir's README.md
- If it does not exist, report the error and stop. Tell the user to run .claude/skills/readme_dir.create/SKILL.md on the dir first

Find the Demo

Find the runner: the executable that runs all stages, or the only executable
- Take its path, flags, and example commands from the README of the dir and of the script
- Check the flags with --help
Find the small example input: the smallest input file that the README or the tests use, e.g., paper_list.short.csv
- Skim the whole file, so the text says what the rows are
Choose the output dir: take it from the README if it gives one. Else use ./run_demo, a dir in the current dir
Find the setup the command needs, e.g., PYTHONPATH, an API key, or Docker. Take it from the README of the dir
Find what the demo needs and costs
- Name the needs: internet, an LLM, a browser, an API key
- Say that the demo costs LLM calls when it calls an LLM
- Do not run a command that costs money. Ask the user to run it
If the runner has --dry_run, run it. Check that it needs no internet, no LLM, and no browser

Read the full file on GitHub · 140 lines

Changes

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.

yesterday First seen · 140 lines · 0 tokens per session scan A dd7ad0bca861

Subscribe to this mod's changes

review.create_demo is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,664 tokens. 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-11-06.

Writing and docs

review.create_demo next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
review.create_demogpsaggese/helpers	Skill	158	today	Apache-2.0	A	0	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	today	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	99k	today	Apache-2.0	A	19	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
chat-pet-sprite-creationmicrosoft/vscode	Skill	195k	today	MIT	A	53	Claude Code, Codex