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 NmadeleiDev/landingforge --skill landing-designgit clone --depth 1 https://github.com/NmadeleiDev/landingforgeWrote 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/nmadeleidev/landingforge/landing-design)<a href="https://agentmods.dev/skills/nmadeleidev/landingforge/landing-design"><img src="https://agentmods.dev/badge/skills/nmadeleidev/landingforge/landing-design/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/nmadeleidev/landingforge/landing-design"><img src="https://agentmods.dev/badge/skills/nmadeleidev/landingforge/landing-design.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.00168 | $0.04065 |
| Opus 5 | $0.00084 | $0.02032 |
| Sonnet 5 | $0.00034 | $0.00813 |
| Haiku 4.5 | $0.00017 | $0.00407 |
Grade A, and why
landing-design 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 9d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running an
lp-*agent on Codex. Codex has no parallel subagent tool, and this pipeline is sequential and gated anyway. Wherever this file says to spawn or run an agent inline, it means: read.codex/agents/<name>.mdand follow its full body verbatim as that phase's operating instructions, one phase at a time.
Landing Page Design (Phase 3, standalone)
Run only phase 3 of the LandingForge pipeline: take a committed strategy
(brief.md) and the page's words (copy.md) and commit them to a visual
system — tokens.css (the machine-readable design system) + design.md (the
human-readable rationale and anti-slop self-check). This is a thin standalone
wrapper around the lp-designer agent. It does not write strategy, copy, or
build a page; it produces the two visual artifacts the build phase renders from
and the scorer judges on the Visual distinctiveness axis (25% of the rubric).
The thesis of LandingForge is that AI ships the statistically-average page because it generates in one shot with no committed point of view — average type, an indigo→violet gradient, three identical cards, flat Tailwind gray. This skill is where the visual POV gets committed: one mood, one accent, one display face — chosen on purpose from calibrated teardowns and written down — so the build phase has a spec to render instead of reaching for generic SaaS or generic app-store defaults.
Path resolution. All
references/…and.codex/agents/…paths below are relative to the plugin root ({{LANDINGFORGE_ROOT}}, the directory containingplugin.json), not to this skill's own folder. The knowledge base and the agent contracts live at the plugin root on purpose — they are the one shared brain every LandingForge skill and agent reads. If a bare path such asreferences/visual-system.mdor.codex/agents/lp-designer.mddoes not resolve from the current directory, prefix it with{{LANDINGFORGE_ROOT}}/.
Same artifacts as the full pipeline. The
tokens.css+design.mdthis skill emits are byte-for-byte the artifactslanding-buildphase 3 produces. A visual system committed here is a valid drop-in for phases 4–8: hand it tolanding-buildand it picks up exactly where this left off. One engine, two entry points.
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.
- 9d ago First seen · 273 lines · 168 tokens per session scan A 742dbc1f965e
landing-design is a skill published in the GitHub repository NmadeleiDev/landingforge (1 stars, last pushed 1mo ago), licensed MIT. It adds 168 tokens to every session and 4,065 once invoked, about $0.0008 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-31.
Other skills, from other repositories
design-system
Design system and visual language for sales funnels. Provides color palettes, typography, spacing, component styles, and theming guidelines for a polished, premium look.
conversion-ux
Conversion-focused UX patterns for sales funnel pages. Apply these patterns to every page to maximize conversion rates. Covers layout, CTA placement, social proof, urgency, and friction reduction.
mobile-responsive
Mobile-first responsive design patterns for sales funnels. Ensures every page works flawlessly on all screen sizes with proper touch targets, readable typography, and fast load times.
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…