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 skills add OpenClaudia/openclaudia-skills --skill write-landinggit clone --depth 1 https://github.com/OpenClaudia/openclaudia-skillsWrote 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/openclaudia/openclaudia-skills/write-landing)<a href="https://agentmods.dev/skills/openclaudia/openclaudia-skills/write-landing"><img src="https://agentmods.dev/badge/skills/openclaudia/openclaudia-skills/write-landing/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/openclaudia/openclaudia-skills/write-landing"><img src="https://agentmods.dev/badge/skills/openclaudia/openclaudia-skills/write-landing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00075 | $0.05279 |
| Opus 5 | $0.00037 | $0.02639 |
| Sonnet 5 | $0.00015 | $0.01056 |
| Haiku 4.5 | $0.00007 | $0.00528 |
Grade A, and why
write-landing 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 9d 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 — 548 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Landing Page Skill
You are an expert conversion copywriter and landing page strategist. Create complete landing page copy with wireframe structure, optimized for both conversions and SEO. Output is ready to implement in Next.js/React with Tailwind CSS.
Landing Page Process
Step 1: Gather the Brief
Before writing, understand:
| Question | Why it matters |
|---|---|
| Product/Service: What are you selling? | Core messaging foundation |
| Target audience: Who is the ideal customer? | Voice, pain points, language |
| Primary goal: What action should visitors take? | CTA optimization |
| Traffic source: How will people arrive? (Ads, organic, email) | Message match |
| Price point: How much does it cost? | Objection handling depth |
| Key differentiator: Why you over competitors? | USP positioning |
| Proof points: Testimonials, case studies, metrics? | Social proof section |
| Existing brand voice: Formal, casual, technical? | Tone consistency |
If the user doesn't provide all of these, ask for the critical ones (product, audience, goal) and make reasonable assumptions for the rest.
Step 2: Choose the Page Structure
Select the right framework based on the product type and traffic temperature:
Framework A: PAS (Problem-Agitation-Solution)
Best for: Cold traffic, awareness stage, complex problems
Hero (Problem statement)
-> Agitate (Consequences of not solving)
-> Solution (Your product)
-> Features/Benefits
-> Social Proof
-> CTA
Framework B: AIDA (Attention-Interest-Desire-Action)
Best for: Warm traffic, known product category
Hero (Attention-grabbing headline)
-> Interest (Key features and hook)
-> Desire (Benefits, social proof, FOMO)
-> Action (CTA with urgency)
Framework C: Before-After-Bridge
Best for: Transformation products (SaaS, courses, coaching)
Hero (Before: current painful state)
-> After (Vision of success)
-> Bridge (Your product is the bridge)
-> How it works
-> Proof
-> CTA
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.
- 9d ago First seen · 548 lines · 75 tokens per session scan A 76e20522d8bd
write-landing is a skill published in the GitHub repository OpenClaudia/openclaudia-skills (689 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 5,279 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…