landing-page-generator-executor.template

landing-page-generator-executor.template is a command for Claude Code from evan043/claude-cli-advanced-starter-pack. It costs 0 tokens per session (1,481 once invoked), scanned A, original, MIT.

A phase-based workflow for building a landing page, a web page designed to guide visitors toward one main action.

In plain words
What is it for?
Use it to execute the phases of a landing-page generator integration when that feature is enabled.
Why use it?
It reads saved progress and identifies the next phase, helping work continue from its current state.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: names the AskUserQuestion tool; mentions Codex.

Good fit Use it to execute the phases of a landing-page generator integration when that feature is enabled.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/evan043/claude-cli-advanced-starter-pack/landing-page-generator-executor.template
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/evan043/claude-cli-advanced-starter-pack

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.

agentmods badge for landing-page-generator-executor.template

README.md
[![agentmods](https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/landing-page-generator-executor.template/github.svg)](https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/landing-page-generator-executor.template)
Your own site
<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/landing-page-generator-executor.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/landing-page-generator-executor.template/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 landing-page-generator-executor.template

Your own site · 80×15
<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/landing-page-generator-executor.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/landing-page-generator-executor.template.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,481 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.01481
Opus 5 $0.00000 $0.00740
Sonnet 5 $0.00000 $0.00296
Haiku 4.5 $0.00000 $0.00148

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

Security

Grade A, and why

landing-page-generator-executor.template 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.

templates/commands/landing-page-generator-executor.template.md · 161 lines

How it starts

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

Codex Runtime Compatibility

This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:

  • AskUserQuestion => ask the user directly in chat.
  • WebSearch/WebFetch => use available web tools (search_query, open, find) and cite links.
  • Read/Write => use shell/filesystem tools in this workspace.
  • Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
  • Keep intent and output format identical; only adapt execution mechanics.

description: Landing Page Generator - Phase Executor model: sonnet allowed-tools:

  • Read
  • Write
  • Edit
  • Bash
  • Task
  • Glob
  • Grep

Landing Page Generator - Phase Executor

{{#if panel_config}} Panel config gate: If panel_config.features.landing_page_generator === false, skip this entire command. Display: "Landing page generator executor skipped (disabled in panel config)." {{/if}}

You are executing phases of the Landing Page Generator feature integration.

Execution Protocol

Step 1: Load Progress State

Read .claude/docs/landing-page-generator/PROGRESS.json to determine current state.

Step 2: Identify Next Phase

Find the first phase with status: "pending" or status: "in_progress".

Step 3: Load Exploration Context

Read the relevant exploration files before executing:

  • .claude/exploration/landing-page-generator/PHASE_BREAKDOWN.md - Detailed task specs
  • .claude/exploration/landing-page-generator/CODE_SNIPPETS.md - Code patterns to follow
  • .claude/exploration/landing-page-generator/REFERENCE_FILES.md - Files to create/modify
  • .claude/exploration/landing-page-generator/AGENT_DELEGATION.md - Agent assignments

Step 4: Execute Phase Tasks

For each pending task in the current phase:

  1. Update task status to in_progress in PROGRESS.json
  2. Execute the task following the PHASE_BREAKDOWN.md specification
  3. Verify acceptance criteria for the task
  4. Update task status to completed in PROGRESS.json

Read the full file on GitHub · 161 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 · 161 lines · 0 tokens per session scan A bdea7ab73422

Subscribe to this mod's changes

landing-page-generator-executor.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,481 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-30.