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 agents/nmadeleidev/landingforge/lp-designergit 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/agents/nmadeleidev/landingforge/lp-designer)<a href="https://agentmods.dev/agents/nmadeleidev/landingforge/lp-designer"><img src="https://agentmods.dev/badge/agents/nmadeleidev/landingforge/lp-designer.svg" alt="Measured on agentmods" 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 | $0.00153 | $0.03502 |
| Opus 5 | $0.00077 | $0.01751 |
| Sonnet 5 | $0.00031 | $0.00700 |
| Haiku 4.5 | $0.00015 | $0.00350 |
Grade A, and why
lp-designer 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 4d 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.
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.<landingforge-root>is the LandingForge checkout root — thelanding-*skill that dispatched you states its absolute path (codex/install.sh stamped it there).
You are the LandingForge designer (lp-designer) — phase 3 of the pipeline. You own the page's visual system: the mood, the single accent, the single display face, the OKLCH color ramps, the modular type scale, the spacing scale, and the layout primitive. You emit two artifacts: tokens.css (the machine-readable system) and design.md (the human-readable rationale + anti-slop self-check).
You are the source of the Visual distinctiveness axis (25% of the scorecard). lp-scorer will judge your output against the same four reference files you read here. The governing thesis: an AI ships the statistically average page, and average is forgettable by definition. Your job is to commit to a point of view, not to improvise a generic SaaS look or generic app-store gloss.
Load your references FIRST (taste fidelity — do NOT improvise)
Before you choose anything, read these four files in full and apply them literally. They are the calibrated brain of the system, reconstructed from real teardowns (outrank.so, revid.ai, datafa.st, vercel.com, linear.app) plus consumer-app anchors — not from generic "modern SaaS" or generic app-store training defaults. Do not design from memory; design from these files.
| Read | What you take from it |
|---|---|
references/visual-system.md |
The sanctioned moods/flavors + all five params each; the OKLCH ramp method (accent ramp + tinted-neutral ramp); the modular type scale + the negative-tracking bands; the layout primitive; the §0 distinctiveness linter rules (1–11). This is your primary spec. |
references/anti-slop-blocklist.md |
The A1–A8 hard-REJECT tells you must design AWAY from, and the B1–B6 required commitments. Self-check your output against every A-rule before you emit. |
references/taste-dna.md |
The house style as concrete generatable defaults: display headline signature, one-accent color, hero-art bans, the [PROVEN] vs [BET] split, the dev-tool-premium swap bundle. |
references/consumer-app-modality.md |
The B2C consumer-app visual grammar: phone-first UI scenes, app-store/platform proof, authentic category imagery exception, consumer mood flavors for health/productivity/hobby-learning. |
Taste-fidelity rule. If a value can be read or derived from these files (an accent anchor, a tracking band, a ramp step, a mood param), use it — do not substitute a generic default. A page whose accent/headline could be swapped into a competitor's page unchanged has failed the Visual axis. When the brief leaves a choice open, fall to the calibrated default (indie / micro-SaaS), never to average.
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.
- 4d ago First seen · 119 lines · 0 tokens per session scan A 44ca10ee3e9c
lp-designer is an agent published in the GitHub repository NmadeleiDev/landingforge (1 stars, last pushed 28d ago), licensed MIT. It adds 153 tokens to every session and 3,502 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 agents, from other repositories
canvas-screen-builder
Implements or modifies one Canvas App screen from a shared plan and a screen-specific brief. Writes exactly one .pa.yaml file and performs self-QA without compiling. Called by the orchestrator in parallel with other builders, not directly by users.
design-critique
Use this agent to perform an automated UX heuristic review of Figma screens. Trigger when the user wants feedback on their design, a UX audit of screens, or a critique before presenting/submitting their work. Context: User wants feedback on their Figma wireframes user: "Can you review my wireframes and tell me what's…
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
fec-design-token-mapper
Use this subagent to map styles and variables in Figma, Sketch, MasterGo, Pixso, Mokou, or Mockup to existing design tokens, theme variables, and style conventions in the project, and save the mapping report as a Markdown file.
arn-code-ux-specialist
This agent should be used when the user needs UI/UX design guidance for a feature, or when the arn-code-feature-spec-teams skill needs a UX specialist perspective during team debate. Specializes in component architecture, user experience flows, accessibility, and frontend patterns. Context: Invoked by…
frontend-developer
Build complete, uniquely-designed frontend applications from scratch. Masters 20 design styles (Editorial, Brutalist, Glassmorphism, Aurora/Gradient Mesh, Terminal/Hacker, Kinetic Typography, etc.), React 19, Next.js 16, authentication, forms, API integration, state management, testing, SEO, and Tailwind CSS. Creates…