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.
npx skills add TheMattBerman/landing-page-factory --skill page-strategygit clone --depth 1 https://github.com/TheMattBerman/landing-page-factoryWrote 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.
[](https://agentmods.dev/skills/themattberman/landing-page-factory/page-strategy)<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.
<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>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.
| Model | Per session | Once 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 |
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.
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.mdor manual brief
Optional:
- source screenshots
- product images
- existing brand profile
- operator notes about page goal
Required output
Write both:
workspace/pages/[page-name]/strategy.mdworkspace/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
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.
- 12d ago First seen · 182 lines · 40 tokens per session scan A b68e952aa4b4
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.
Other skills, from other repositories
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
officecli-word-form
Use this skill to create fillable Word forms (.docx) with real Content Controls (SDT) + legacy FormField checkboxes + MERGEFIELD mail-merge placeholders + document protection. Trigger on: 'fillable form', 'form fields', 'content controls', 'SDT', 'word form', 'fill in', 'only editable fields', 'protect document'…
summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
add-matrix
Add Matrix channel integration via Chat SDK. Works with any Matrix homeserver.
add-resend
Add Resend (email) channel integration via Chat SDK.
add-macos-statusbar
Add a macOS menu bar status indicator for NanoClaw. Shows a bolt icon with a green/red dot indicating whether NanoClaw is running, with Start, Stop, and Restart controls. macOS only.