wp-cinematic-demo

wp-cinematic-demo is a command for Claude Code from yojahny55/claude-wp-builder. It costs 0 tokens per session (1,038 once invoked), scanned A, original, MIT.

A command that generates a self-contained, cinematic scrolling HTML demo for client approval before the design is connected to WordPress.

In plain words
What is it for?
Use it to create or regenerate a demo with scroll-driven scenes, optional brand input, videos, posters, and standard sections such as pricing or contact.
Why use it?
It gives the client a reviewable version of the site and keeps its sections compatible with later polishing and responsive checks.

Command for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the claude-wp-builder plugin — 15 skills, 30 commands, 15 agents shipped together

Good fit Use it to create or regenerate a demo with scroll-driven scenes, optional brand input, videos, posters, and standard sections such as pricing or contact.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add yojahny55/claude-wp-builder
Claude Code
/plugin install claude-wp-builder

Made for: Claude Code.

Or install claude-wp-builder, the plugin that ships this one along with the rest of its 15 skills, 30 commands, 15 agents.

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.

agentmods badge for wp-cinematic-demo

README.md
[![agentmods](https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-cinematic-demo/github.svg)](https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-cinematic-demo)
Your own site
<a href="https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-cinematic-demo"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-cinematic-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.

agentmods 80×15 button for wp-cinematic-demo

Your own site · 80×15
<a href="https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-cinematic-demo"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-cinematic-demo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,038 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01038
Opus 5 $0.00000 $0.00519
Sonnet 5 $0.00000 $0.00208
Haiku 4.5 $0.00000 $0.00104

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

Security

Grade A, and why

wp-cinematic-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.

commands/wp-cinematic-demo.md · 83 lines

How it starts

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

/wp-cinematic-demo

Produces a self-contained, scroll-driven demo HTML at <theme>/demo/index.html plus demo/assets/{css,js,videos,posters}/. The demo is what you send the client for approval BEFORE wiring WordPress.

Step 0.5: Read the craft layer

Read ${CLAUDE_PLUGIN_ROOT}/skills/wp-demo-craft/SKILL.md and its taste.md, feel.md and fingerprint.md first. They set the design floor, the feeling curve with one engineered peak, and the fingerprint gate that apply to a cinematic demo exactly as they do to a static one. The kit's own skills supply the video-specific rules on top: scene encoding, the scrub engine, mobile substitution.

Where the two disagree, the craft layer wins on design and the kit wins on video. Scene numbers in HUD labels are optional here, not required: a 01 / 06 counter is a slop finding from npx -y impeccable@4 detect — pinned to the major version for the reason references/verify.md gives — unless the sequence information is something the reader needs.

Pipeline

  1. Resolve kit path (same logic as /wp-cinematic-init step 0).
  2. Invoke kit skill 04-build-cinematic-scroll-site:
    skill: 04-build-cinematic-scroll-site
    args:
      scenes: <N>
      out_dir: <theme>/demo
      brand_brief: <--brand path or empty>
      hybrid: <true|false>
    
  3. Kit emits raw demo (its native templates/index.html, main.js, style.css skeleton).
  4. Post-process for plugin compatibility:
    • Wrap each scene with <!-- SECTION: scene-N --> ... <!-- END SECTION --> delimiters so /wp-section and /wp-polish recognize them.
    • Wrap trailing blocks with <!-- SECTION: pricing -->, <!-- SECTION: contact -->, etc.
    • Inject the standard <!-- DEMO: name=cinematic, archetype=cinematic-scroll, hybrid=true --> header comment so /wp-init demo-first detection picks it up.
  5. If --brand provided, dispatch kit skill 01-narrative-from-brand first; pipe its narrative into 02-storyboard-from-narrative; feed the storyboard scenes into the demo generator (instead of placeholders).
  6. Generate placeholder videos by symlinking the kit's sample reels into demo/assets/videos/ (do NOT copy — saves disk).
  7. Open demo/index.html in the user's browser via wp-open helper, or print the file:// path.

Read the full file on GitHub · 83 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.

  1. yesterday Changed · +1 lines fbb857ddba93
  2. 6d ago Changed · +14 lines c15d9969b85a
  3. 11d ago First seen · 68 lines · 0 tokens per session scan A 94391bc2c274

Subscribe to this mod's changes

wp-cinematic-demo is a command published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,038 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-08-31.

Related

Other commands, from other repositories