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 instructions/monthu56/landforge/claude-mdgit clone --depth 1 https://github.com/monthu56/landforgeWrote 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/instructions/monthu56/landforge/claude-md)<a href="https://agentmods.dev/instructions/monthu56/landforge/claude-md"><img src="https://agentmods.dev/badge/instructions/monthu56/landforge/claude-md.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.00812 | $0.00812 |
| Opus 5 | $0.00406 | $0.00406 |
| Sonnet 5 | $0.00162 | $0.00162 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
landforge CLAUDE.md 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code working on this system (the landing-generation toolkit itself).
Human overview: README.md. Decisions: docs/adr/.
What this is
A content-management / generation system for static landing pages, delivered as Claude Code skills + deployment infra. Not a build-tooling project (no bundler, test runner, lint).
Hard invariant: a landing is a static HTML file with content in the markup and zero JS on the critical path (CSS/JS inlined). Crawlers must see real content, not an empty root. Every generator and skill must preserve this.
Skills (.claude/skills/)
new-landing— landing from a brief (contract + skeleton +check_landing.py).landing-experiment— A/B on one URL (inline split, no cloaking), variant tracking, card.landing-journal— audit journal:experiments/journal.jsonl+journal.md+ git. Log every meaningful action viascripts/log_event.py.landing-ads— UTM, ad copy, keywords, editor exports →ads/<campaign>/(artifacts only).init-landing-system— deploy this whole system into another project (snapshot + sync + user-level install).
MCP server (mcp/)
The toolbox is also exposed as an MCP server (ADR-0002) — any MCP host can call it, not only
Claude Code. Thin wrapper: each tool runs the same .claude/skills/*/scripts/*.py via subprocess
(one source of logic). Validators / journal / UTM as tools; contract, brief schema, skeleton
and journal as resources; brief interviewer / generation / A/B checklist as prompts.
Transport stdio; optional dependency (Python ≥ 3.10, mcp); the
static-HTML invariant is untouched. New skill script → add a matching tool (keep CLI↔MCP parity).
See mcp/README.md.
Infra & deployment
.github/workflows/deploy.yml routes by branch: main → prod (indexable); dev → staging
(noindex); any other → preview (noindex). Server runs Traefik + two nginx containers; only prod
is indexed (X-Robots-Tag: noindex on staging via nginx). Infra values are {{PLACEHOLDER}}s
(domains/containers/dirs) — substituted by init-landing-system or by hand
(.claude/skills/init-landing-system/reference/placeholders.md). Deploy secrets: DEPLOY_HOST,
DEPLOY_USER, DEPLOY_SSH_KEY, DEPLOY_KNOWN_HOSTS.
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 · 55 lines · 812 tokens per session scan A 799a40e66401
landforge CLAUDE.md is an instructions file published in the GitHub repository monthu56/landforge (10 stars, last pushed 3mo ago), licensed MIT. It adds 812 tokens to every session, about $0.0041 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 instructions, from other repositories
builder-growth CLAUDE.md
Instructions for RBraga01/builder-growth, covering builder-growth — claude configuration, pack version, file conventions, skill trigger sequence and agent usage.
builder-growth AGENTS.md
Instructions for RBraga01/builder-growth, covering builder-growth — agent directory, growth-critic, experiment-designer, messaging-reviewer and growth-strategist.
marketingskills AGENTS.md
AGENTS.md instructions for coreyhaines31/marketingskills, covering agents.md, repository overview, repository structure, build / lint / test commands and versioning.
aso-skills AGENTS.md
AGENTS.md instructions for Eronred/aso-skills, covering agent guidelines, structure, skill.md format, writing style and app store reference.
pruna-skills AGENTS.md
AGENTS.md instructions for PrunaAI/pruna-skills, covering pruna skills (agent notes), how it works, clarification (library-wide), install and layout.
faf-one-svelte-new AGENTS.md
Instructions for Wolfe-Jam/faf-one-svelte-new, covering agents.md — faf-one-svelte, setup & build, where things live, conventions and guardrails.