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-qagit 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-qa)<a href="https://agentmods.dev/skills/themattberman/landing-page-factory/page-qa"><img src="https://agentmods.dev/badge/skills/themattberman/landing-page-factory/page-qa/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-qa"><img src="https://agentmods.dev/badge/skills/themattberman/landing-page-factory/page-qa.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.00726 |
| Opus 5 | $0.00020 | $0.00363 |
| Sonnet 5 | $0.00008 | $0.00145 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
page-qa 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Page QA
This is the final gate. It exists because good-looking pages can still be strategically wrong, untrustworthy, or impossible to ship.
Required inputs
workspace/pages/[page-name]/strategy.jsonworkspace/pages/[page-name]/copy.mdworkspace/pages/[page-name]/index.htmlworkspace/pages/[page-name]/meta.jsonworkspace/pages/[page-name]/visuals/index.mdworkspace/pages/[page-name]/visuals/manifest.jsonwhen presentreferences/anti-slop.md
QA dimensions
Score each 1-10 unless pass/fail is more appropriate.
1. Mechanism preservation
- is the unique mechanism visible and understandable?
- does the page explain why this works?
- did aesthetics overpower explanation?
2. Proof discipline
- are all stats, testimonials, logos, guarantees, and claims provenance-tagged?
- is anything non-shippable still presented as real?
3. Trust cue preservation
- were critical trust conventions preserved?
- were category-legitimacy cues kept intact?
4. Copy sharpness
- specificity
- fluff control
- objection coverage
- CTA clarity
5. Visual fidelity
- correct preservation class use
- no fake precision where exactness was required
- no obvious artifacts
- provider fallback history is reflected honestly in metadata when relevant
6. Build quality
- responsive structure
- contrast
- semantics
- focus states
- alt text
7. Anti-slop compliance
- no banned patterns
- anti-slop used without overriding brand fidelity
Output format
Write workspace/pages/[page-name]/qa.md:
# QA Report: [page-name]
Generated:
| Dimension | Score | Threshold | Result | Notes |
|---|---:|---:|---|---|
| mechanism preservation | | 8 | pass/fail | |
| proof discipline | | 9 | pass/fail | |
| trust cue preservation | | 8 | pass/fail | |
| copy sharpness | | 8 | pass/fail | |
| visual fidelity | | 8 | pass/fail | |
| build quality | | 8 | pass/fail | |
| anti-slop compliance | | 8 | pass/fail | |
## Hard fails
-
## Draft-only flags
-
## Required fixes before ship
1.
2.
3.
## Verdict
- shippable
- draft only
- blocked
What ships with it
2 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 · 119 lines · 40 tokens per session scan A 9983165bef92
page-qa 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 726 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.