Hermes logo
Hermes Agent template
x.com

Local Landing Page Agency

A Hermes agent that runs a local web-design agency end to end — inspiration-first briefs, branded Astro landing pages, cold-email previews, Stripe payment, live on the client domain.

NewNew48.2 KB snapshotStarter VM

What's inside

Harness

Hermes Agent

Plan

Starter

vCPU

1

Memory

2 GiB

Snapshot

48.2 KB

How it works · ~3 minutes

  1. 01 · Fork

    New isolated microVM on your subdomain — creator state included.

  2. 02 · Your keys

    Log into Hermes Agent with your own model credentials (BYOK).

  3. 03 · Ask it to work

    Open the terminal and give it a real job. You keep what ships.

30-day money-back on your first purchase · no free trial · keys never leave the VM

About this template

Local Landing Page Agency — in a box (Hermes)

Fork this and your Hermes agent is a one-person local web-design agency. It runs the whole loop:

find → inspire → brief → design → preview → cold-email → get paid → serve.

Agency-grade design process

Most AI site builds open the editor and guess at “beautiful.” This agent does the process real $10k landing pages use:

  1. Inspiration first — shortlist 3–5 real reference sites (trade competitors + Landbook / Siteinspire / etc.).
  2. Creative brief (BRIEF.md) — frankenstein specifics: “layout from A, palette from B, type from C — not the dark theme from D.” Screenshots live in refs/.
  3. Plan before code — short section plan, then tokens.
  4. DESIGN.md tokens — Google design.md protocol → Tailwind v4 @theme → Astro static site.
  5. When round one is wrong, fix the brief — don’t thrash components.

Plus the conversion stack local service businesses need: benefit-led hero, trust bar, tap-to-call, real reviews, short quote form.

Full agency loop

  • Designs a real, branded Astro + Tailwind landing page for a local business (HVAC, legal, dental, contractors).
  • Cold-outreaches with the build-first playbook: builds the site before pitching, emails a live preview from Hermes’s native mailbox — personalized, low-volume, with unsubscribe.
  • Weekly drip until reply or unsubscribe (Hermes-native cron).
  • Charges via Stripe Payment Links and serves live on the client’s domain once they pay (Caddy on your box, or Vercel).
  • One git repo per client, with BRIEF.md + DESIGN.md + status ladder (prospect → preview → live → paid).

What you bring (BYOK — nothing is baked into the template)

Set these in ~/.hermes/.env after forking:

  • OPENROUTER_API_KEY — your Hermes model key (hermes config set OPENROUTER_API_KEY …, then hermes model).
  • Email: hermes gateway setup → your dedicated sending mailbox (address + app-password + IMAP/SMTP hosts).
  • STRIPE_SECRET_KEY — your own Stripe account (charges your clients).
  • A hosting target — a Caddy VPS you control (SSH) or a Vercel Pro token. See the host-deploy skill.
  • Optional GH_TOKEN to push each client repo to your GitHub.

node + headless-Chrome ship in the image; per-client npm install runs at build time.

The undeniable demo

Tell it: "Build a landing page for Phoenix Desert HVAC." It shortlists references, writes a BRIEF.md, plans the page, writes a DESIGN.md, generates a branded Astro site (tap-to-call, trust bar, reviews, quote form), builds a preview, and drafts the outreach email with the preview link — end to end.

Skills: design-site, cold-outreach, stripe-billing, host-deploy, client-repo, screenshot.

Process inspiration: Remy — landing page process.

Inside this fork

Forking copies this template into a brand-new, fully isolated microVM on your own subdomain. Here's exactly what lands in it.

  • Hermes Agent agent

    The upstream harness, pre-installed — same version the creator ran.

  • Starter VM

    1 vCPU · 2 GiB RAM · 10 GiB disk.

  • Creator's /persist data

    The captured persist volume is copied byte-for-byte into your fork.

  • BYOK — your keys, your VM

    Add your model API keys after forking; they live only inside your microVM.

What this agent can do

6 skills

  • client-repo

    One git repository per client — the convention that keeps 500 clients organized, versioned, rollback-able, and handoff-ready. Each repo…

  • cold-outreach

    Run the "build first, sell after" local-agency playbook — pre-build a landing page for a local business, email them a live preview link via…

  • design-site

    Design and build a high-converting landing page for a local service business (HVAC, dentist, lawyer, contractor) as a real static Astro +…

  • host-deploy

    Host every client's static site on its own custom domain with automatic HTTPS, operated entirely by the agent over shell. Primary path is…

  • screenshot

    Capture a clean desktop + mobile screenshot of a rendered site — for warm-reply previews, the "your site is live" email, and a visual…

  • stripe-billing

    Charge the client through the forker's own Stripe account and gate "serve the live site" on payment clearing. Use when proposing pricing,…

What you'll configure after forking

Secrets are scrubbed from shared templates — these are the names you supply in your agent's terminal once it boots.

Environment variables

  • DEPLOY_TARGET
  • EMAIL_ADDRESS
  • EMAIL_IMAP_HOST
  • EMAIL_PASSWORD
  • EMAIL_SMTP_HOST
  • GH_TOKEN
  • OPENROUTER_API_KEY
  • STRIPE_SECRET_KEY

Your turn

Your own Local Landing Page Agency, live in about 3 minutes.

Forking copies this Hermes Agentagent into a brand-new, fully isolated microVM on your own subdomain — the creator's /persist state and all. Add your own keys after it boots; they never leave the box. Don't love it? Your first jurniti purchase comes with 30 days to get every cent back.

New paid VM · BYOK · 30-day money-back on your first purchase · ~3 min to provision

Starter · fork

$25/ mo

Needs 8 of your own API keys