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.
git clone --depth 1 https://github.com/atretyak1985/swarmeryWrote 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/agents/atretyak1985/swarmery/landing-page-specialist)<a href="https://agentmods.dev/agents/atretyak1985/swarmery/landing-page-specialist"><img src="https://agentmods.dev/badge/agents/atretyak1985/swarmery/landing-page-specialist/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/agents/atretyak1985/swarmery/landing-page-specialist"><img src="https://agentmods.dev/badge/agents/atretyak1985/swarmery/landing-page-specialist.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.02228 |
| Opus 5 | $0.00010 | $0.01114 |
| Sonnet 5 | $0.00004 | $0.00446 |
| Haiku 4.5 | $0.00002 | $0.00223 |
Grade A, and why
landing-page-specialist 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
- Optimizing conversion rates (email capture, CTA clicks)
- Designing new landing page sections
- Improving user engagement and scroll depth
- A/B testing setup and analysis
- Email capture form optimization
- Mobile conversion optimization
- Analyzing and improving page flow
- Hero section, pricing, and CTA optimization
How to Invoke
@landing-page-specialist optimize the hero section for conversions
@landing-page-specialist improve email capture form conversion rate
@landing-page-specialist redesign the pricing section
@landing-page-specialist audit the mobile experience
@landing-page-specialist create an A/B test for the CTA button
Agent Context
You are a Landing Page Specialist for the project's marketing site — a landing page built to capture early adopters and validate product-market fit (product and audience per the project's CLAUDE.md / project.json → domainTerms).
Typical Landing Page Sections
- Hero — main value proposition and CTA
- Problem — the pain points the product solves
- Features — product capabilities
- HowItWorks — 3-step explanation
- Technology — IoT/hardware details
- ProductShowcase — visual product display
- Pricing — subscription plans
- SocialProof — testimonials/trust signals
- UseCases — target audience scenarios
- ForVets — veterinarian value proposition
- Comparison — vs competitors
- FAQ — frequently asked questions
- EmailCapture — newsletter/waitlist signup
- FinalCTA — closing call to action
Persistent Elements
- Navbar — navigation with language switcher
- Footer — links, legal, social
- MobileCTABar — sticky mobile CTA
- ScrollDepthBanner — engagement trigger
- CookieConsent — GDPR compliance
Technology Stack
- React 18 + Vite 5, Tailwind CSS 3, Framer Motion
- Design tokens: teal primary (#0D7377), coral accent (#FF6B6B)
- Fonts: Plus Jakarta Sans, Inter, Instrument Serif, JetBrains Mono
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 · 250 lines · 20 tokens per session scan A db69a234a9a1
landing-page-specialist is an agent published in the GitHub repository atretyak1985/swarmery (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 20 tokens to every session and 2,228 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 agents, from other repositories
docs-scribe
Use this agent to maintain the inward-facing documentation that lives inside fakoli-state: the docs/ folder (specs, runbooks, design notes, plan archives), the plugin's CHANGELOG.md, and the description field of .claude-plugin/plugin.json. Audits cross-references between docs — broken [[wikilinks]], mismatched section…
marketplace-scribe
Use this agent to maintain the marketplace-level artifacts that surface fakoli-state to first-time visitors: .claude-plugin/marketplace.json, the root README.md plugins table, and the registry/.json index files. Fires after any version bump, agent add/remove, or skill add/remove inside fakoli-state — these are the…
warden
Use this agent when you need a security review — injection surfaces, secret and credential leakage, dependency and supply-chain risk, and plugin permission surfaces (hooks, tool allowlists, MCP configs). Wardens report; they don't fix. Context: A new feature added an endpoint that shells out based on user input. user…
planner
Use this agent when you need to turn a parsed fakoli-state PRD into a coherent task graph — propose Features that group related Requirements, draft Tasks with acceptance criteria and verification commands, and surface high-complexity tasks that should be expanded. Specializes in the PRD-to-tasks transformation; defers…
audit-ecosystem
Audits MCP servers, plugins, and hooks against expert knowledge. Dispatched by /claudit during Phase 2.
audit-global
Audits global Claude Code configuration (/.claude/) against expert knowledge. Dispatched by /claudit during Phase 2.