wp-cinematic-init

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

A setup command for a cinematic WordPress theme built around scrolling through scenes while a video stage changes over time.

In plain words
What is it for?
Use it to start this type of site from an existing demo or from scratch, install or locate the cinematic kit, and hand the remaining setup to the standard WordPress initializer.
Why use it?
It prepares the specialized theme structure and supporting kit needed for desktop scroll-scrubbing, mobile playback, and reduced-motion behavior.

Command for Claude Code

Written for Claude Code: arguments in frontmatter.

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

Good fit Use it to start this type of site from an existing demo or from scratch, install or locate the cinematic kit, and hand the remaining setup to the standard WordPress initializer.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/yojahny55/claude-wp-builder/wp-cinematic-init
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.

Clone the repo
git clone --depth 1 https://github.com/yojahny55/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-init

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-cinematic-init"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-cinematic-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 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,137 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.00076 $0.01137
Opus 5 $0.00038 $0.00568
Sonnet 5 $0.00015 $0.00227
Haiku 4.5 $0.00008 $0.00114

Measured 9d ago against content hash 4afc703db667, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

wp-cinematic-init 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 9d 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.

commands/wp-cinematic-init.md · 101 lines

How it starts

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

/wp-cinematic-init

Use this when the demo is not a standard sectioned page but a cinematic scroll-driven reel: persistent video stage, N scenes that crossfade/scrub as the user scrolls, mobile autoplay-loop fork, motion-toggle, reduced-motion guard.

This command is a thin shim. It does three things and hands off:

Step 0 — Detect kit

Check in order:

  1. Globally-installed skill: ~/.skills/yojahny55/cinematic-scroll-kit/schemas/scene.json
  2. Project-local: ./.cinematic-kit/schemas/scene.json
  3. Vendored fallback inside the plugin: <plugin>/starter-theme/__cinematic__/assets/cinematic-kit/schemas/scene.json

If none found AND --skip-kit-install not set → run:

npx skills add yojahny55/cinematic-scroll-kit -g -y

If npx skills is unavailable, fall back to:

git clone --depth 1 https://github.com/yojahny55/cinematic-scroll-kit .cinematic-kit

If both fail → use vendored fallback and log: "Using vendored kit copy (offline mode). Update later with /wp-cinematic-init --update-kit."

Step 1 — Hand off to /wp-init

Invoke /wp-init --path=<path> --mode=cinematic --starter=__cinematic__ --acf-flavor=<scf|acf-pro> and let the standard bootstrap run:

  • Project name/slug/text domain/languages
  • Server choice (Nginx native, Docker, etc.)
  • Database
  • ACF flavor

When /wp-init reaches the "section scaffolding" phase, it skips the usual /wp-section loop and instead dispatches to step 2 below.

Step 2 — Cinematic scaffold (dispatch wp-cinematic agent)

Pass to the wp-cinematic agent:

{
  "schema_path": "<resolved kit path>/schemas/scene.json",
  "project_slug": "<from /wp-init>",
  "text_domain": "<from /wp-init>",
  "languages": ["en", "es"],
  "acf_flavor": "<scf|acf-pro>",
  "scene_count": 9,
  "hybrid": true
}

The agent produces every file listed in its Outputs you produce table.

Step 3 — Wire and seed

  1. Activate the theme via wp theme activate <slug>.
  2. Run wp eval-file inc/seed-cinematic.php to populate the placeholder scenes.
  3. Run wp eval-file inc/seed-menus.php if menus haven't been seeded yet.
  4. Print next steps:
    • Replace placeholder videos: /wp-cinematic-encode <input.mp4> --scene=N
    • Author scene content: /wp-cinematic-scene <n>
    • Add trailing sections (pricing/contact): /wp-section <name> --hybrid
    • Preview demo: /wp-cinematic-demo

Read the full file on GitHub · 101 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. 9d ago First seen · 101 lines · 76 tokens per session scan A 4afc703db667

Subscribe to this mod's changes

wp-cinematic-init is a command published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 1,137 once invoked, about $0.0004 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.

Related

Other commands, from other repositories