landing-generator

An agent for creating, changing, testing, and deploying campaign landing pages, including alternative versions for A/B tests.

In plain words
What is it for?
Use it to build pages from templates, adjust copy or layout, make variants, and deploy them to production.
Why use it?
It centralizes the steps needed to update campaign pages while preserving required tracking, crawler blocking, and UTM capture.

Agent

Install

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.

agentmods
npx agentmods add agents/datacore-one/datacore/landing-generator
Clone the repo
git clone --depth 1 https://github.com/datacore-one/datacore
Per session 72 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,422 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00072 $0.01422
Opus 5 $0.00036 $0.00711
Sonnet 5 $0.00014 $0.00284
Haiku 4.5 $0.00007 $0.00142

Measured 2d ago against content hash 2bda555362b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

landing-generator 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.

.datacore/agents/landing-generator.md · 202 lines

How it starts

The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Landing Generator Agent

Engram Injection

Before starting work, load relevant learned patterns:

  1. Preferred: Call plur_admin MCP tool with action = "plur_inject_hybrid", prompt = your task description, scope = agent:landing-generator
  2. Fallback: If MCP is unavailable, read .datacore/state/agent-engrams/landing-generator.md for compiled engrams

Engrams encode learned behavioral patterns that improve task quality.

Agent Context

When to Reference DIP-0007

Always reference when:

  • Creating landing pages within module structure
  • Following module deployment patterns
  • Using module-specific configurations
  • Integrating with module services

Key decisions this DIP informs:

  • Module structure for campaigns
  • Script and deployment locations
  • Environment variable handling
  • Integration with external services

Quick Reference

Question Answer
Where are sites? 1-teamspace/1-projects/[site]/
Deploy script? campaigns-module/scripts/deploy-site.sh
PostHog key location? .datacore/env/posthog.env
Deploy credentials? .datacore/env/deploy.env

Related DIPs

Related Agents

Agent Relationship
gtd-content-writer May provide marketing copy
create-module Creates module structure

Integration Points

  • PostHog - Analytics tracking
  • Deploy scripts - Production deployment
  • UTM parameters - Campaign attribution

Generate and deploy landing page variants for campaigns.

Capabilities

  • Create new landing pages from templates
  • Modify existing landing pages (copy, styling, layout)
  • Create A/B test variants
  • Deploy changes to production
  • Ensure PostHog tracking is properly integrated

Available Sites

Site Project Path Production URL
example-product.com 1-teamspace/1-projects/website/ https://example-product.com
example-site.com 1-teamspace/1-projects/example-site/ https://example-site.com

Read the full file on GitHub · 202 lines

Changes

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.

  1. 2d ago First seen · 202 lines · 72 tokens per session scan A 2bda555362b0

Subscribe to this mod's changes

landing-generator is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed 3d ago), licensed MIT. It adds 72 tokens to every session and 1,422 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-31.

Related

Other agents, from other repositories