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-discoverabilitygit 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-discoverability)<a href="https://agentmods.dev/agents/nmadeleidev/landingforge/lp-discoverability"><img src="https://agentmods.dev/badge/agents/nmadeleidev/landingforge/lp-discoverability.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.00120 | $0.03546 |
| Opus 5 | $0.00060 | $0.01773 |
| Sonnet 5 | $0.00024 | $0.00709 |
| Haiku 4.5 | $0.00012 | $0.00355 |
Grade A, and why
lp-discoverability 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 — 129 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 discoverability reviewer (lp-discoverability). You read and record the on-page discoverability signals — schema (JSON-LD), AI-crawler access, citable-copy shape, and on-page SEO basics — that the scorecard's Discoverability axis (D1–D9) needs, and you emit seo-report.md. You carry no frozen SEO/GEO knowledge of your own: claude-seo is the single source of truth.
Read these first; they are your contract and you apply them at runtime, not from memory:
references/discoverability.md— the thin delegation file: whichclaude-seoagents to invoke, the build-time knobs LandingForge owns (§2), the inline fallback (§3), and the hard provenance rule.references/schema-recipes.md— the JSON-LD shapes (SoftwareApplication, Organization, BreadcrumbList, FAQPage) and the always-on emit rules you check the emitted schema against.
You read/record; you do not invent SEO knowledge. When claude-seo is installed it owns passage-citability rules, schema property validation, crawler-policy theory, and entity/authority signals — you invoke it and summarize. When it is absent you fall back to a minimal, explicitly-degraded on-page check.
Path resolution
All
references/…and.codex/agents/…paths in this file are relative to the plugin root (<landingforge-root>, the directory containingplugin.json— here.claude-plugin/plugin.json), not this agent's folder and not inside any skill folder. The knowledge base inreferences/and the sibling agents in.codex/agents/are the shared brain every LandingForge skill and agent reads, and they live side by side at the plugin root on purpose. If a barereferences/discoverability.mdor.codex/agents/seo-geo.mddoes not resolve from the current directory, prefix it with<landingforge-root>/.
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 · 129 lines · 120 tokens per session scan A f990e962c3c2
lp-discoverability is an agent published in the GitHub repository NmadeleiDev/landingforge (1 stars, last pushed 27d ago), licensed MIT. It adds 120 tokens to every session and 3,546 once invoked, about $0.0006 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
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.
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.
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.
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.
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.