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 tmj-90/gaffer --skill landing-page-generatorgit clone --depth 1 https://github.com/tmj-90/gafferWrote 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/tmj-90/gaffer/landing-page-generator)<a href="https://agentmods.dev/skills/tmj-90/gaffer/landing-page-generator"><img src="https://agentmods.dev/badge/skills/tmj-90/gaffer/landing-page-generator/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/tmj-90/gaffer/landing-page-generator"><img src="https://agentmods.dev/badge/skills/tmj-90/gaffer/landing-page-generator.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.00097 | $0.00899 |
| Opus 5 | $0.00048 | $0.00449 |
| Sonnet 5 | $0.00019 | $0.00180 |
| Haiku 4.5 | $0.00010 | $0.00090 |
Grade A, and why
landing-page-generator 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 10d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate high-converting landing pages
Not lorem ipsum — actual copy and structure that converts. Output complete, ready-to-ship TSX components with Tailwind.
Performance targets: LCP ≤ 2.5s · CLS < 0.1 · INP < 200ms
Copy frameworks
Pick one per page — don't mix:
| Framework | Structure | Best for |
|---|---|---|
| PAS | Problem → Agitate → Solution | Pain-aware traffic; problem-first messaging |
| AIDA | Attention → Interest → Desire → Action | Cold traffic; brand-new product |
| BAB | Before → After → Bridge | Transformation products; outcome-led |
Section blueprint (in order)
- Hero — headline (value prop in ≤ 10 words) + subheadline (1 sentence expanding on the outcome) + primary CTA + social proof signal (count or logo strip).
- Problem / Pain — articulate the cost of the status quo in the user's own language.
- Solution / Features — 3–6 benefits (not feature names); each benefit has a one-line explanation.
- Social proof — testimonials with name, role, company; star ratings if applicable; logos.
- Pricing (if applicable) — 2–4 tiers; highlight the recommended one; FAQ accordion.
- FAQ — answer the 5 objections that would stop a user converting; include FAQ schema markup.
- Footer CTA — repeat the primary CTA; reduced friction (email-only, not full form).
Steps
- Gather inputs. Before writing: product name, tagline, primary audience, key pain point, main benefit, primary CTA label, design style (pick one: minimal light / editorial dark / neo-brutalist / SaaS clean). Ask for missing fields — one question at a time.
- Choose copy framework. Based on traffic source and audience awareness level.
- Write copy first, structure second. Headline variants: write 5, pick the clearest (not the cleverest). Subheadline must state the outcome, not the mechanism.
- Build sections in order. Hero → social proof → problem → solution → pricing → FAQ → footer CTA. Each section is a standalone TSX component.
- SEO meta. Title tag (≤ 60 chars), meta description (≤ 160 chars), OG tags, canonical.
- Performance. Hero image:
loading="eager" fetchpriority="high". Everything below the fold:loading="lazy". Fonts:font-display: swap; preload only the critical weight. - Verify. Type-check (
tsc --noEmit); Lighthouse score on desktop; confirm LCP < 1s; record evidence.
What ships with it
1 file 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.
- 10d ago First seen · 62 lines · 97 tokens per session scan A 320ef7d4d04c
landing-page-generator is a skill published in the GitHub repository tmj-90/gaffer (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 97 tokens to every session and 899 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-31.
Other skills, from other repositories
react-developer
Expert knowledge in React development, hooks, state management, and modern React patterns.
bulwark-brainstorm
Role-based brainstorming with dual modes: --scoped (sequential Task tool, 5 roles) and --exploratory (Agent Teams peer debate, 4 roles). Use for feasibility assessment and idea validation.
plan-creation
Create structured implementation plans via a 4-role scrum team (Product Owner, Architect, Eng/Delivery Lead, QA/Critic) with optional Agent Teams peer debate mode.
anthropic-validator
Validates Claude Code assets (skills, hooks, agents, commands, MCP servers, plugins) against official Anthropic standards. Fetches latest docs dynamically and produces structured validation reports.
create-subagent
Generates single-purpose Claude Code sub-agents for use via the Task tool. Use when creating dedicated sub-agents, scaffolding agent definitions, or generating agents with diagnostics and permissions setup.
test-audit
Audit test suites for T1-T4 violations using AST analysis, mock detection, and multi-stage synthesis. Invoke when user asks to audit tests, check test quality, find mock violations, review test effectiveness, or inspect test suites for over-mocking. Triggers automatic rewrites when quality gates fail.