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-buildgit 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-build)<a href="https://agentmods.dev/skills/themattberman/landing-page-factory/page-build"><img src="https://agentmods.dev/badge/skills/themattberman/landing-page-factory/page-build/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-build"><img src="https://agentmods.dev/badge/skills/themattberman/landing-page-factory/page-build.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.00036 | $0.01305 |
| Opus 5 | $0.00018 | $0.00652 |
| Sonnet 5 | $0.00007 | $0.00261 |
| Haiku 4.5 | $0.00004 | $0.00130 |
Grade A, and why
page-build 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.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Page Build
Build quality comes after strategic fidelity, not before it.
This stage assembles the page while preserving what matters for trust and conversion.
Required inputs
workspace/pages/[page-name]/strategy.jsonworkspace/brand/profile.mdworkspace/brand/palette.jsonworkspace/pages/[page-name]/copy.mdworkspace/pages/[page-name]/visuals/references/anti-slop.md(bundled with this skill)
If strategy is missing, stop.
If workspace/pages/[page-name]/visuals/manifest.json exists, use it as the canonical machine-readable visual source.
Do not ignore provider metadata when it affects trust, fidelity, or fallback history.
Preservation hierarchy
Apply in this order:
- preserve trust-critical category conventions
- preserve mechanism communication needs
- preserve brand visual identity
- improve layout rhythm and interaction quality
- apply anti-slop taste improvements only where they do not distort 1-4
Anti-slop is a quality filter, not a redesign license.
Pre-build checklist
Before generating HTML, confirm:
- page type confirmed
- conversion mechanism confirmed
- proof inventory loaded
- trust cues selected
- visual manifest resolved into build-ready image paths
- required category conventions preserved
- CTA destination known
- layout choice justified in one line
If any are false, stop or downgrade.
Routing logic
Physical product route
Use when strategy page type is product-led.
Above fold must include:
- clear product or mechanism visual
- offer headline
- CTA
- trust cue
SaaS / app route
Above fold must include:
- preserved screenshot or UI treatment if required
- outcome headline
- trust cue
- CTA
Lead capture route
Above fold must include either:
- form + friction reducer or
- clear CTA into a known destination
Authority / service route
Must include:
- authority cue above fold
- proof section early
- objection handling around trust and fit
Regulated route
Must include:
- downgraded certainty when proof is partial
- compliance review flag in metadata
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 205 lines · 36 tokens per session scan A a3dff3be6e76
page-build is a skill published in the GitHub repository TheMattBerman/landing-page-factory (40 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 1,305 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
add-clidash
Add clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group…
frontend-engineer
Pro frontend engineering discipline. Enforces build-test-verify workflow for every web project. Never declare done until the site is built, tested, responsive, accessible, and visually verified in a real browser. Pairs with a deployment skill such as vercel-cli, where one is installed.
frontend-conventions
Coding conventions, architecture patterns, and testing rules for the SkillHub React frontend. Ensures agents follow Feature-Sliced Design and use the generated OpenAPI types.
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
miniapp-dev
A development guide for BitFun MiniApps, which are small applications that run inside BitFun. It covers creating new MiniApps as well as maintaining the MiniApp framework.
redteam-cors-miscfg-detail-pack
Domain routing and boundary guidance for authorized CORS misconfiguration testing, including reflected origins, null origins, subdomain trust, and credential exposure. Use when a task belongs to the CORS testing domain and needs scope, evidence, pivot, or exit criteria.