page-strategy

page-strategy is a skill for Claude Code, Codex from TheMattBerman/landing-page-factory. It costs 40 tokens per session (872 once invoked), scanned A, original, MIT.

A planning step that turns a website brief or extracted source material into a page strategy. It records the offer, audience, proof, call to action, content decisions, and items that must be preserved.

In plain words
What is it for?
Planning landing pages and other website pages, deciding the conversion goal, mapping the customer problem and solution, and documenting safe proof and review points.
Why use it?
It clarifies what a page should say and show before writing copy or building it, while flagging claims that need evidence.

Skill for Claude CodeCodex

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

Good fit Planning landing pages and other website pages, deciding the conversion goal, mapping the customer problem and solution, and documenting safe proof and review points.

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

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 page-strategy

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/themattberman/landing-page-factory/page-strategy"><img src="https://agentmods.dev/badge/skills/themattberman/landing-page-factory/page-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 872 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.00040 $0.00872
Opus 5 $0.00020 $0.00436
Sonnet 5 $0.00008 $0.00174
Haiku 4.5 $0.00004 $0.00087

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

Security

Grade A, and why

page-strategy 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 12d 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/page-strategy/SKILL.md · 182 lines

How it starts

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

Page Strategy

This is the missing operator layer.

site-extract collects facts. page-strategy decides what must be preserved, what can change, what proof is safe to use, and what page type should be built.

No strategy artifact, no page.

Inputs

Required:

  • workspace/brand/extract.md or manual brief

Optional:

  • source screenshots
  • product images
  • existing brand profile
  • operator notes about page goal

Required output

Write both:

  • workspace/pages/[page-name]/strategy.md
  • workspace/pages/[page-name]/strategy.json

Strategy schema

# Page Strategy: [page-name]
Brand:
Page type:
Built:
Confidence:

## 1. Core decision
- Product / service:
- Offer:
- Audience:
- Awareness stage:
- CTA action:
- CTA destination:
- Conversion goal:

## 2. Mechanism map
- Primary buyer job:
- Primary pain:
- Failed alternatives:
- Unique mechanism:
- Why the mechanism works:
- What must be shown visually:
- What must be explained verbally:

## 3. Claims control
### Allowed claims
- [claim] — provenance class

### Forbidden claims
- [claim]

### Claims requiring proof near them
- [claim]

## 4. Proof plan
| Proof item | Class | Provenance | Where it should appear | Shippable? |
|---|---|---|---|---|

## 5. Preservation plan
### Trust cues to preserve
- 

### Visual conventions to preserve
- 

### Language to preserve
- exact phrases
- category terms buyers expect
- differentiators in source wording

### Deviations allowed
- what can be improved safely

## 6. Page routing
- Recommended page type:
- Hero structure:
- Proof structure:
- CTA strategy:
- Objection strategy:
- Required sections:
- Optional sections:

## 7. Visual requirements
- Visual preservation class: exact product / branded environment / concept support
- Screenshot handling: required / optional / forbidden
- Packaging fidelity needed? yes/no
- UI fidelity needed? yes/no
- Product silhouette fidelity needed? yes/no

## 8. Review flags
- compliance-sensitive claims
- thin proof
- missing CTA destination
- visual asset gaps
- any human approval needed

Read the full file on GitHub · 182 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. 12d ago First seen · 182 lines · 40 tokens per session scan A b68e952aa4b4

Subscribe to this mod's changes

page-strategy is a skill published in the GitHub repository TheMattBerman/landing-page-factory (40 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 872 once invoked, about $0.0002 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-30.