Borrowing it
Nothing to install: this file belongs to dkadts/landing-kit-building. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dkadts/landing-kit-building/main/CLAUDE.mdgit clone --depth 1 https://github.com/dkadts/landing-kit-buildingWrote 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/dkadts/landing-kit-building/claude-md)<a href="https://agentmods.dev/instructions/dkadts/landing-kit-building/claude-md"><img src="https://agentmods.dev/badge/instructions/dkadts/landing-kit-building/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.1 | $0.01316 | $0.01316 |
| Opus 5 | $0.00658 | $0.00658 |
| Sonnet 5 | $0.00263 | $0.00263 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
landing-kit-building 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 8d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Kit — Protocol for AI Agents
A universal system for building landing pages. Vanilla HTML/CSS/JS + Vercel. Primary CTA is a request form (no payment integrations).
7 rules (default for all sessions)
-
Strict isolation. Edit only the files the user named explicitly or that clearly belong to the current task. Do not "improve" adjacent code.
-
DESIGN-LOCK.md is frozen. If a field is marked
LOCKED— do not change it. Change only through explicit user override with an entry in the decision log. -
No hardcode. All colors, sizes, paddings, fonts, easing, duration — from
site/css/tokens.css. If a value is missing — first add it to tokens (with user approval), then use it. Hardcodedpx/#hex/msin CSS or JS is blocked. -
Algorithmic approach. Paddings and sizes — via Flexbox / Grid /
calc()/vw. No "by eye". -
User owns commits. Do not run
git add,commit,push,reset— the user versions manually. -
Typography discipline (English). No hanging short words at line end (articles, prepositions, conjunctions, auxiliaries, short pronouns, dashes) — tie them to the following word with
. No orphans — the last line of a heading or paragraph must have ≥ 2 words. Print-typography rules apply. Enforcement via/typography, called automatically by/buildand checked by/audit. English-only; do not run on other languages. -
References priority. Every element approved during
/refs,/design-lock,/animation, or/iconsbecomes a required entry inreferences/approved-manifest.md./buildwill not save a section that omits a relevant manifest item./auditfails on any unchecked item. Silent drops are the failure mode this rule exists to prevent — always ask the user to remove an item explicitly with a decision-log entry.
Workflow for a new landing (mandatory order)
1. /brief Survey + brief. First question: desktop-first or mobile-first
2. /inbox Sort client materials from inbox/
3. /copy-analyze Deep text analysis → brief/copy-analysis.md
4. /refs References parsed by aspect + approved-manifest.md
5. /design-lock FREEZE DESIGN-LOCK.md (spacing, type, color, motion, ...)
6. /blocks Config for interactive blocks (form, modal, chat, ...)
7. /animation Motion brief → brief/animation.md (appends to manifest)
8. /tokens Generate site/css/tokens.css from DESIGN-LOCK
9. /media Media pipeline (WebP/AVIF, resize, posters)
10. /icons Hybrid icons: libraries + AI fallback (appends to manifest)
11. /build Section assembly (guard against slop + hardcode + manifest coverage + typography pass)
12. /mobile Mobile adaptation with hardened rules + safety check
13. /audit Anti-slop + perf + a11y + typography + references compliance
14. /deploy Vercel + optional GCP Secret Manager for sensitive keys
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.
- 8d ago First seen · 94 lines · 1,316 tokens per session scan A 627180ea84d7
landing-kit-building CLAUDE.md is an instructions file published in the GitHub repository dkadts/landing-kit-building (2 stars, last pushed 19d ago), licensed MIT. It adds 1,316 tokens to every session, about $0.0066 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.