landing-page-visuals

landing-page-visuals is a skill for Claude Code, Codex from canvora/canvora-mcp. It costs 70 tokens per session (1,256 once invoked), scanned A, original, MIT.

A skill for generating a set of images for a website landing page from its URL, including visuals for sections such as the hero, features, process, and call to action.

In plain words
What is it for?
It helps create visual kits for landing pages, including hero images, feature illustrations, process visuals, statistics, testimonials, comparisons, timelines, and CTA imagery.
Why use it?
It removes the need to plan and create each page visual separately while keeping the images matched to the page's content and style.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: built for openclaw.

Good fit It helps create visual kits for landing pages, including hero images, feature illustrations, process visuals, statistics, testimonials, comparisons, timelines, and CTA imagery.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/canvora/canvora-mcp/landing-page-visuals
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 canvora/canvora-mcp --skill landing-page-visuals
Clone the repo
git clone --depth 1 https://github.com/canvora/canvora-mcp

Made for: Claude Code, Codex.

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-visuals

README.md
[![agentmods](https://agentmods.dev/badge/skills/canvora/canvora-mcp/landing-page-visuals/github.svg)](https://agentmods.dev/skills/canvora/canvora-mcp/landing-page-visuals)
Your own site
<a href="https://agentmods.dev/skills/canvora/canvora-mcp/landing-page-visuals"><img src="https://agentmods.dev/badge/skills/canvora/canvora-mcp/landing-page-visuals/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-visuals

Your own site · 80×15
<a href="https://agentmods.dev/skills/canvora/canvora-mcp/landing-page-visuals"><img src="https://agentmods.dev/badge/skills/canvora/canvora-mcp/landing-page-visuals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,256 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.00070 $0.01256
Opus 5 $0.00035 $0.00628
Sonnet 5 $0.00014 $0.00251
Haiku 4.5 $0.00007 $0.00126

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

Security

Grade A, and why

landing-page-visuals 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 11d 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.

skills/landing-page-visuals/SKILL.md · 115 lines

How it starts

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

Landing page visual kits

Canvora has a section-aware mode that nothing else in the toolchain does: give it a URL and it reads the page's actual sections, decides which ones deserve a visual, and renders a matching kit. One command, a whole page's imagery, in the page's own language.

Requires the Starter plan or higher — a 403 here means the plan, not auth. Setup and credits: see the canvora skill.

The one command

ID=$(canvora generate --url https://example.com --landing-page \
  --brand $BRAND --logo | head -1)
canvora status "$ID" --json    # repeat every ~30s until completed

--format is not required in this mode: the kit is derived from the page. --landing-page requires --url (it has nothing to read otherwise).

A kit is up to 10 visuals, so fire-and-poll rather than --wait — most harnesses kill a shell command at 120s while the kit carries on rendering server-side. Never re-run generate after a timeout; poll status (detail in the canvora skill's "Long runs" section). Say the cost in the same message as the run: 10 credits per visual, so a full kit is up to 100. Announce it, don't ask permission — but if the page could yield the full 10 and they only wanted a hero, settle that first.

What it produces, and what it deliberately skips

The pipeline maps sections onto these formats:

Format Section
landingPage-Hero 21:9 hero banner
landingPage-Feature feature blocks
landingPage-Process how-it-works
landingPage-Showcase product showcase
landingPage-Stats metrics / proof
landingPage-Testimonial quotes
landingPage-Comparison vs / before-after
landingPage-Timeline roadmap / history
landingPage-CTA closing call to action
landingPage-UseCase never auto-emitted — name it explicitly to get it

Caps and guarantees, so you can set expectations before spending credits:

  • at most 10 sections and 10 visuals per run; at most 5 per section
  • hero and CTA are never trimmed — everything else competes for slots
  • FAQ, team, contact, footer and logo walls are intentionally skipped: they are not visual sections. If the user wants one anyway, generate it as a normal format in a separate call.

Read the full file on GitHub · 115 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. 11d ago First seen · 115 lines · 70 tokens per session scan A 87866bb2e18f

Subscribe to this mod's changes

landing-page-visuals is a skill published in the GitHub repository canvora/canvora-mcp (0 stars, last pushed 29d ago), licensed MIT. It adds 70 tokens to every session and 1,256 once invoked, about $0.0003 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.