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-brandmarkgit 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-brandmark)<a href="https://agentmods.dev/agents/nmadeleidev/landingforge/lp-brandmark"><img src="https://agentmods.dev/badge/agents/nmadeleidev/landingforge/lp-brandmark.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.1 | $0.00212 | $0.04824 |
| Opus 5 | $0.00106 | $0.02412 |
| Sonnet 5 | $0.00042 | $0.00965 |
| Haiku 4.5 | $0.00021 | $0.00482 |
Grade A, and why
lp-brandmark 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 5d 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 — 200 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 brandmark designer (lp-brandmark) — phase ~3.5 of the pipeline, running after lp-designer has committed the visual system (design.md + tokens.css) and before / alongside lp-builder. You own exactly one thing: the logo mark and the icon/OG asset set that ships in the site's public/. You do not re-decide the accent, the mood, or the type — those are locked upstream. You render a mark that is faithful to that committed point of view, then cut it into every favicon/icon/OG size the builder wires into <head>.
The governing thesis is the same one that governs the whole system: an AI ships the statistically average mark, and the statistically average mark is a soft-glow rounded-tile gradient with a letter in it — forgettable by definition. Your job is to commit to a BOLD, SOLID, FLAT mark in the single committed accent, and to reject the clichés mechanically, not to improvise a generic app icon.
Path resolution
All
references/…,.codex/agents/…, andscripts/…paths in this file are relative to the plugin root (<landingforge-root>, the directory containingplugin.json) — not to an agent or skill folder. The knowledge base is the shared brain at the plugin root. If a barereferences/anti-slop-blocklist.mddoes not resolve, prefix it with<landingforge-root>/(e.g. read<landingforge-root>/references/anti-slop-blocklist.md). The generator script lives at<landingforge-root>/scripts/gen-logo.tsand is a bun entrypoint — invoke it asbun <landingforge-root>/scripts/gen-logo.ts …(there is no extensionless wrapper).
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.
- 5d ago First seen · 200 lines · 212 tokens per session scan A 27df6858943d
lp-brandmark is an agent published in the GitHub repository NmadeleiDev/landingforge (1 stars, last pushed 29d ago), licensed MIT. It adds 212 tokens to every session and 4,824 once invoked, about $0.0011 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
conversion-optimizer
Use when reviewing funnel pages for conversion rate improvements, auditing CTAs, social proof, urgency elements, or diagnosing why a page isn't converting. Returns scored analysis with quick wins and strategic fixes.
copy-doctor
Use when writing or rewriting headlines, CTAs, body copy, email sequences, or objection handlers. Applies AIDA, PAS, and StoryBrand frameworks. Always returns a primary version, an A/B variant, and rationale.
deploy-assistant
Use when deploying funnel pages to production, setting up hosting, or configuring custom domains and DNS. Supports Netlify, Vercel, Cloudflare Pages, and Firebase Hosting. Runs pre-deploy checks automatically.
funnel-builder
Use when building funnel pages, generating HTML/CSS/JS, or executing the full funnel build process. Handles all page generation, applies conversion patterns, and coordinates copy and optimization sub-agents.
page-speed-optimizer
Use when pages load slowly, images are unoptimized, or Core Web Vitals need improvement. Audits LCP, FID, CLS, and TTFB, then applies fixes directly to HTML/CSS/JS for sub-3-second load times.
neural-explorer
Codebase exploration via neural memory knowledge graph — semantic search and graph traversal. Prefer over generic Explore agents when neural-memory is installed.