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 lovstudio/skills --skill product-onepagegit clone --depth 1 https://github.com/lovstudio/skillsWrote 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/lovstudio/skills/product-onepage)<a href="https://agentmods.dev/skills/lovstudio/skills/product-onepage"><img src="https://agentmods.dev/badge/skills/lovstudio/skills/product-onepage/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/lovstudio/skills/product-onepage"><img src="https://agentmods.dev/badge/skills/lovstudio/skills/product-onepage.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.00106 | $0.02483 |
| Opus 5.5 | $0.00042 | $0.00993 |
| Sonnet 5.5 | $0.00021 | $0.00497 |
| Haiku 4.5 | $0.00011 | $0.00248 |
Grade A, and why
lov-product-onepage 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 23d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
产品一页纸 · Product OnePage
Build one public product story on one fixed canvas. Combine brand positioning, conversion narrative, evidence discipline, product staging, and code-rendered typography. Do not turn a Landing Page into a screenshot or an infographic into a card wall.
source truth
→ public/private ledger
→ Brand Spine + one public thesis
→ headline spine + conversion
→ layout × art direction
→ real product stage + supporting visual
→ editable HTML/SVG master
→ render + machine gate
→ full-size and thumbnail review
→ independently recomposed derivatives
Default to a 4:5 master at 1080 × 1350. Recompose 9:16, 1:1, 16:9, and
A4 derivatives; never crop or uniformly shrink the master.
Required outcome
Deliver:
- one recognizable product thesis, not a feature inventory;
- clear category, audience relevance, product mechanism, proof cue, and action;
- one dominant product stage using a real screenshot, artifact, output, or an explicitly conceptual representation;
- one real CTA destination or an explicitly labeled availability state;
- public claims mapped to evidence IDs; unknowns remain internal;
- exact HTML/SVG text for product name, claims, dates, prices, Logo, and CTA;
- text-free generated imagery only when it improves the product story;
- editable
onepage.html, high-resolutiononepage.png,source.md,brief.md,content.md,project.json, prompt record, andaudit.json; - a recorded human review at original size and thumbnail size.
Reject generic three-card layouts, unsupported superlatives, fake product UI, decorative prompt boxes, dead CTA buttons, synthetic testimonials, baked-in critical text, and output accepted only because it renders.
Read before authoring
Read all four references:
references/content-system.md— truth ledger, Brand Spine, headline spine, proof, and conversion.references/layouts.md— semantic OnePage layouts and DOM contracts.references/art-direction.md— visual systems, product staging, and hybrid image-generation policy.references/quality-gate.md— machine and human release criteria.
What ships with it
14 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.
- .gitignore 33 B
- agents/openai.yaml 271 B
- assets/brand-logo.svg 726 B
- assets/brand-profile.template.json 440 B
- assets/onepage-template.html 13 KB
- CHANGELOG.md 295 B
- references/art-direction.md 2.7 KB
- references/config.md 1.3 KB
- references/content-system.md 3.3 KB
- references/layouts.md 2.8 KB
- references/quality-gate.md 1.9 KB
- scripts/onepage_cli.py 45 KB runs code
- scripts/test_onepage_cli.py 4.6 KB runs code
- skill.yaml 842 B
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.
- 23d ago First seen · 283 lines · 106 tokens per session scan A 347031db35db
lov-product-onepage is a skill published in the GitHub repository lovstudio/skills (72 stars, last pushed 5d ago), licensed MIT. It adds 106 tokens to every session and 2,483 once invoked, about $0.0004 per session on Opus 5.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-09-26.
Other skills, from other repositories
openai-frontend-design
Use for new frontend applications, dashboards, games, creative websites, hero sections, and visually driven UI from scratch, or when the user explicitly asks for a redesign/restyle/modernization. Builds from clean, airy, high-taste, readable image-generated concept design with section-specific references, faithful…
ultralytics-branding
This skill should be used when creating Ultralytics-branded content of any kind, including PDF, PPTX, Canva, or Google Slides presentations, DOCX documents, marketing or newsletter HTML emails, social media post copy or visuals, website or landing page designs, and dataset or model result visuals. Provides official…
shadcn
Current best-practices guide for shadcn/ui applications. Before applying primitive-specific guidance, inspect whether the checked-in components use Radix UI or Base UI; current shadcn supports both (Base UI is the default for new projects) and their composition APIs differ. Component installs and upgrades go through…
poster-style-transfer
Analyze an uploaded or local reference poster, extract its reusable design system, and transpose that system to an original poster with a new theme, title, subtitle, or campaign copy.
grill-design
Decide a UI design by building several genuinely different working prototypes and comparing them side by side, in rounds, until the choice is locked. Use when asked to "grill the design", "design this screen", "show me options", "prototype some variants", "what should this look like", "I can't decide on a layout".
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".