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 subhansh-dev/agent-maxxing --skill workflow-landing-pagegit clone --depth 1 https://github.com/subhansh-dev/agent-maxxingWrote 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/subhansh-dev/agent-maxxing/workflow-landing-page)<a href="https://agentmods.dev/skills/subhansh-dev/agent-maxxing/workflow-landing-page"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/workflow-landing-page/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/subhansh-dev/agent-maxxing/workflow-landing-page"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/workflow-landing-page.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.00020 | $0.00603 |
| Opus 5 | $0.00010 | $0.00302 |
| Sonnet 5 | $0.00004 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
workflow-landing-page 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 5d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Agent Workflow: Landing Page Sprint
Ship a conversion-optimized landing page in one day using agent skills.
The Scenario
You need a landing page for a new product. It needs to look great, convert visitors, and be live by end of day.
Skills Used
| Skill | Role in this workflow |
|---|---|
| Frontend Design | Design the layout and component specs |
| Writing Style | Write the copy |
| Artifact Design | Visual identity and polish |
| Anti-Patterns | Avoid AI-generated looks |
| Polish | Final quality pass |
The Workflow
Step 1: Research & Plan
Load Frontend Design skill.
Analyze the product and target audience.
Decide: hero style, color palette, typography, layout structure.
Output: Design brief with specific choices.
Step 2: Write Copy (Parallel)
Load Writing Style skill.
Write landing page copy:
1. Hero (headline + subheadline + CTA)
2. Problem statement (3 pain points)
3. How it works (3 steps)
4. Social proof (testimonial format)
5. Pricing (3 tiers)
6. Final CTA
Tone: confident, concise, slightly playful.
Avoid: AI slop words, hedging, sycophantic openers.
Step 3: Build Layout
Load Frontend Design + Artifact Design skills.
Build the HTML/CSS:
- Hero with real image (not SVG gradient)
- Feature cards with icons (not emoji)
- Pricing table with clear hierarchy
- Mobile-responsive throughout
- No purple-blue gradients
- No glassmorphism everywhere
Step 4: Apply Anti-Slop
Load Anti-Patterns skill.
Check for:
- Purple-to-blue gradients? → Replace
- Identical card grids? → Add variety
- "Leverage synergies" copy? → Rewrite
- Inter/Roboto fonts? → Pick something better
- Everything centered? → Add asymmetry
Step 5: Polish
Load Polish skill.
Final pass:
- Spacing consistency
- Typography hierarchy
- Color contrast
- Animation timing
- Loading states
- Error states
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.
- 5d ago First seen · 97 lines · 20 tokens per session scan A 5437042bc235
workflow-landing-page is a skill published in the GitHub repository subhansh-dev/agent-maxxing (2 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 603 once invoked, about $0.0001 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
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
frame-build-minimal
Luxury-minimal whitespace hero — single word reveals letter by letter, warm-gold hairline, breathing indicators.
frontend-design
A design and coding guide for building distinctive web interfaces, including pages, dashboards, landing pages, and reusable components.
component-design
Apply a coherent visual system, responsive behavior, interaction states, and accessibility to Kun components.
uicraft
Create, improve, audit, and polish distinctive production-grade web interfaces, including marketing/landing pages and personal portfolio sites. Use for UI or frontend design, responsive layouts, typography, color, motion, UX copy, accessibility, performance, design-system alignment, onboarding, edge cases, or visual…
design-system-starter
Create and evolve design systems with design tokens, component architecture, accessibility guidelines, and documentation templates. Ensures consistent, scalable, and accessible UI across products.