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 agentmods add skills/agentic-dev3o/devx-plugins/building-landing-pagenpx skills add agentic-dev3o/devx-plugins --skill building-landing-pagegit clone --depth 1 https://github.com/agentic-dev3o/devx-pluginsWhat 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 | $0.00077 | $0.01766 |
| Opus 5 | $0.00039 | $0.00883 |
| Sonnet 5 | $0.00015 | $0.00353 |
| Haiku 4.5 | $0.00008 | $0.00177 |
Grade A, and why
building-landing-page 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 2d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building Landing Page
Generates a production-ready Astro 5 + Tailwind CSS v4 landing page from structured copywriting content.
Copy this checklist and track progress:
Build Progress:
- [ ] Phase 1: Copywriting input validated
- [ ] Phase 2: Project scaffolded (astro config, package.json, tailwind)
- [ ] Phase 3: Base layout and global styles created
- [ ] Phase 4: Navbar and Footer components created
- [ ] Phase 5: Section components generated from copy
- [ ] Phase 6: Index page assembled
- [ ] Phase 7: Build verified
Phase 1: Validate Input
Check that structured copywriting content exists. It should contain sections with this format:
## [Section Name]
> **Psychology**: [principle]
### Headline
### Subheadline / Supporting
### Body
### CTA (if applicable)
If no copywriting exists yet, suggest running the writing-landing-page-copy skill first.
Confirm with the user:
- Project path: Where to generate the project
- Brand customization: Logo text/SVG, primary color (default:
#3b00ff), font (default: Inter), site URL, organization name - Sections to build: Which sections from the copy to implement
Phase 2: Scaffold Project
Generate the Astro 5 project. Follow the setup in project-setup.md exactly.
Create these files:
package.json- Astro 5, Tailwind v4, Node adapter, sitemapastro.config.mjs- SSR mode with Node adapter + Tailwind vite plugintsconfig.json- Strict mode with@/path aliassrc/styles/global.css- Tailwind v4 imports + theme variables
Run bun install after scaffolding.
Phase 3: Base Layout and Global Styles
Create src/layouts/Base.astro with:
- Full SEO meta tags (OG, Twitter, canonical)
- Google Fonts link (Inter by default)
- JSON-LD Organization schema (use site URL and organization name from Phase 1)
- Global CSS classes for effects (gradient-text, btn-glow, card-hover, hero-glow)
<slot />for page content
Follow the design system defined in design-system.md for all color tokens, typography, spacing, and effect classes.
What ships with it
3 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.
- 2d ago First seen · 197 lines · 77 tokens per session scan A 587e030aed85
building-landing-page is a skill published in the GitHub repository agentic-dev3o/devx-plugins (11 stars, last pushed 14d ago), licensed MIT. It adds 77 tokens to every session and 1,766 once invoked, about $0.0004 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
design-guide
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
author-component
Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable…
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…