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 FlorianBruniaux/claude-code-plugins --skill landing-page-generatorgit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/florianbruniaux/claude-code-plugins/landing-page-generator)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/landing-page-generator"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/landing-page-generator.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.01786 |
| Opus 5 | $0.00024 | $0.00893 |
| Sonnet 5 | $0.00010 | $0.00357 |
| Haiku 4.5 | $0.00005 | $0.00179 |
Grade A, and why
landing-page-generator 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 8d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Page Generator
Generate a complete, deploy-ready landing page from any repository by analyzing its documentation and structure.
When to Use This Skill
- Creating a landing page for a GitHub repository
- Generating static sites from existing documentation
- Standardizing landing pages across multiple projects
- Converting README content to marketing/showcase pages
What This Skill Does
- Analyze Repository: Read README.md, CHANGELOG.md, package.json/VERSION, docs/, assets/
- Extract Content: Identify title, tagline, features, installation, screenshots
- Map to Sections: Hero, Features, Install, FAQ, Footer (+ optional: Risk Banner, Pricing)
- Generate Landing: Create complete static site (HTML + CSS + JS)
- Deploy-Ready Output: Include GitHub Actions workflow for GitHub Pages
How to Use
Basic Usage
/landing-page-generator from ~/path/to/repo
With Options
/landing-page-generator from ~/path/to/repo --risk-banner --pricing-table
Available Options
| Option | Description | Default |
|---|---|---|
--risk-banner |
Add prominent warning/disclaimer banner above fold | false |
--pricing-table |
Include pricing comparison section | false |
--screenshots <path> |
Path to screenshots folder | ./assets/ |
--theme [dark|light] |
Color theme variant | dark |
--search |
Enable Cmd+K search | true |
--output <path> |
Output directory | ./[repo-name]-landing/ |
Workflow
Step 1: Repository Analysis
Read and analyze these files from the source repo:
README.md → Primary content source (title, tagline, features, install)
CHANGELOG.md → Version info, recent changes
package.json → Version number, dependencies, metadata
VERSION → Alternative version source
docs/ → Additional documentation pages
assets/ → Screenshots, images
LICENSE → License type for badge
Step 2: Content Extraction Map
| Source | Target Section | Extraction Method |
|---|---|---|
| README title/badges | Hero | First H1 + shield.io badge lines |
| README TL;DR | Hero tagline | First paragraph or blockquote after title |
| README features | Features grid | H2/H3 sections with bullet lists |
| README install | Quick Start | Code blocks with shell commands |
| README usage | Examples | Code blocks with examples |
| README FAQ | FAQ | Details/summary or H3+P patterns |
| CHANGELOG | What's New | Latest 1-3 releases |
| assets/*.png | Screenshots | Gallery section |
What ships with it
12 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.
- assets/search-base.js 11 KB runs code
- assets/section-snippets/faq.html 1.6 KB
- assets/section-snippets/features-grid.html 1.9 KB
- assets/section-snippets/footer.html 1.1 KB
- assets/section-snippets/header.html 1.8 KB
- assets/section-snippets/hero.html 1.4 KB
- assets/section-snippets/install.html 2.2 KB
- assets/section-snippets/risk-banner.html 629 B
- assets/section-snippets/search-modal.html 1.4 KB
- assets/static-workflow.yml 1.2 KB
- assets/styles-base.css 18 KB
- references/landing-pattern.md 11 KB
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.
- 8d ago First seen · 241 lines · 48 tokens per session scan A 0eb51899d3c8
landing-page-generator is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 6d ago), licensed MIT. It adds 48 tokens to every session and 1,786 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
cache-components
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.
performance-optimization
Optimize frontend and backend performance through profiling, caching strategies, database optimization, code splitting, and Core Web Vitals improvements. Build fast user experiences.
coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
frontend-ui-ux
Designer-turned-developer expertise for crafting stunning UI/UX even without design mockups.
frontend-patterns
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.