Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/skills/ooiyeefei/ccc/landing-page-gtm)<a href="https://agentmods.dev/skills/ooiyeefei/ccc/landing-page-gtm"><img src="https://agentmods.dev/badge/skills/ooiyeefei/ccc/landing-page-gtm/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ooiyeefei/ccc/landing-page-gtm"><img src="https://agentmods.dev/badge/skills/ooiyeefei/ccc/landing-page-gtm.svg" alt="Reviewed on agentmods" width="80" 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.00109 | $0.01667 |
| Opus 5 | $0.00055 | $0.00834 |
| Sonnet 5 | $0.00022 | $0.00333 |
| Haiku 4.5 | $0.00011 | $0.00167 |
Grade A, and why
landing-page-gtm 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 11d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Page GTM
Build conversion-focused landing pages that sell — not just describe. Combine product research, competitive positioning, sales copywriting, and frontend implementation into a single workflow.
Intake — Always Ask First
Before any work, collect these inputs:
| Input | Question |
|---|---|
| Target URL | "What URL or route is this for?" (e.g., myapp.com/pricing) |
| Codebase path | "Where's the source code?" (e.g., /home/user/project/src) |
| Product/feature | "What product or feature is this page selling?" |
| Audience | "Who's the buyer? (role, company size, pain level)" |
| Competitors | "Who do they compare you against?" |
| Constraints | "Existing design system, form provider, CTA destination?" |
If the page already exists, read it first. Never propose changes to code you haven't read.
Workflow
Phase 1: Research the Product
Study the actual product before writing a single word of copy. Never invent features.
- Read the codebase — Search for the feature's implementation. Use git log to find recent changes.
- Validate claims — For every claimed feature, confirm it exists in code. Report gaps: "X exists. Y is partial. Z not found."
- Identify differentiators — What does this do that competitors genuinely don't? Architectural advantages > surface features.
- Find the self-improving angle — Any learning/adaptive behavior is marketing gold. Understand the mechanism so you can describe it without jargon.
Phase 2: Competitive Positioning
Frame every section as "why us, not them" without naming competitors.
Positioning formula:
Pain they feel daily
+ What competitors do about it (poorly)
+ What you do differently
+ Outcome they'll experience
Anti-generic test — If copy could appear on a competitor's site unchanged, rewrite it:
- "AI-powered" → What does the AI actually DO?
- "Smart automation" → What specifically gets automated?
- "Easy to use" → Compared to what painful alternative?
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 149 lines · 109 tokens per session scan A 10cb13eae550
landing-page-gtm is a skill published in the GitHub repository ooiyeefei/ccc (489 stars, last pushed 1mo ago), licensed MIT. It adds 109 tokens to every session and 1,667 once invoked, about $0.0005 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-30.
Other skills, from other repositories
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…