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 skills/agentic-dev3o/devx-plugins/writing-landing-page-copynpx skills add agentic-dev3o/devx-plugins --skill writing-landing-page-copygit clone --depth 1 https://github.com/agentic-dev3o/devx-pluginsWrote 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/agentic-dev3o/devx-plugins/writing-landing-page-copy)<a href="https://agentmods.dev/skills/agentic-dev3o/devx-plugins/writing-landing-page-copy"><img src="https://agentmods.dev/badge/skills/agentic-dev3o/devx-plugins/writing-landing-page-copy.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.00057 | $0.01192 |
| Opus 5 | $0.00028 | $0.00596 |
| Sonnet 5 | $0.00011 | $0.00238 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
writing-landing-page-copy 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Page Copywriting
Copy this checklist and track progress:
Workflow Progress:
- [ ] Phase 1: Discovery interview completed
- [ ] Phase 1: Brief confirmed by user
- [ ] Phase 2: Sections selected
- [ ] Phase 3: Copy generated for all selected sections
- [ ] Phase 4: Review pass completed
- [ ] Phase 4: User approved final copy
Phase 1: Discovery Interview
Conduct a detailed interview before writing any copy. Use AskUserQuestion to gather information in 2-3 rounds.
Round 1: Product & Market
Ask these questions together:
- Product: What is the product/service? What does it do in one sentence?
- ICP (Ideal Customer Profile): Who is the primary buyer? (role, company size, industry)
- Core problem: What painful problem does this solve? What happens if they do nothing?
- Main differentiator: What makes this different from alternatives? Why would someone switch?
Round 2: Value & Proof
- Top 3 benefits: What are the three biggest outcomes customers get? (use numbers if possible)
- Process: How does it work? Describe the user journey in 3 steps max
- Social proof: What credibility signals exist? (customer logos, stats, testimonials, awards)
- Pricing model: How is it priced? Any free tier or trial?
Round 3: Strategy & Tone
- Primary CTA goal: What action should visitors take? (sign up, book demo, start trial, buy)
- Urgency triggers: Any legitimate scarcity? (limited seats, launch pricing, beta access)
- Tone adjustment: Default is professional SaaS. Any preference? (bold, casual, technical, enterprise)
After gathering answers, summarize the brief back to the user for confirmation before writing.
Phase 2: Section Selection
Present the available sections and let the user choose which to generate. Default to all.
| # | Section | Purpose |
|---|---|---|
| 1 | Hero | First impression - headline, subheadline, CTA |
| 2 | Trust Bar | Authority logos and social proof |
| 3 | Loss Aversion | Pain amplification before solution |
| 4 | Benefits | Outcome-focused value (rule of 3) |
| 5 | Process | How it works in 3 steps |
| 6 | Features | Technical proof and specs |
| 7 | Pricing | Plans, tiers, value framing |
| 8 | Testimonials | Social proof with specifics |
| 9 | FAQ | Objection handling |
| 10 | Final CTA | Closing push with urgency |
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.
- 4d ago First seen · 150 lines · 57 tokens per session scan A c2a9e75615f5
writing-landing-page-copy is a skill published in the GitHub repository agentic-dev3o/devx-plugins (11 stars, last pushed 16d ago), licensed MIT. It adds 57 tokens to every session and 1,192 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…