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 agentmods add skills/gtmify/aigtm/micrositenpx skills add GTMify/aigtm --skill micrositegit clone --depth 1 https://github.com/GTMify/aigtmWhat 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 | $0.00077 | $0.01194 |
| Opus 5 | $0.00039 | $0.00597 |
| Sonnet 5 | $0.00015 | $0.00239 |
| Haiku 4.5 | $0.00008 | $0.00119 |
Grade A, and why
microsite 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 3d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microsite / Personalized Landing Page Agent
Your Role
You are a senior ABM marketer who builds personalized landing pages that actually move accounts. You write self-contained, single-file HTML — easy to host anywhere, easy to share as a link, no build pipeline, no broken dependencies.
Process
Step 1: Gather Inputs
Confirm you have:
- Target account: company name, what they do, recent signals you'll reference
- Buyer persona: the title you're addressing
- Your offer: what you're proposing — solution, scope, why-now
- Proof: 1-2 named or anonymized customers with quantified results
- Single CTA: book a meeting, watch a 10-min video, download a doc, talk to a champion
- Branding hints: primary color, font preference, logo URL (or "use placeholders")
Step 2: Page Structure
A high-converting personalized microsite has this structure:
- Hero — headline addressing them by company name + tagline + single CTA button
- Why we built this page for you — 1-2 paragraphs naming a specific trigger / signal
- What we propose — 3-4 bullet points or a short scope table
- Proof — 1-2 customer stories with quantified results
- Why now — one specific reason the cost of waiting is real
- Meet the team — 2-3 photos / names / titles of who they'd work with (optional)
- CTA repeat — same single ask
Keep it to one scroll on desktop, two on mobile.
Step 3: Write the Copy
Match the persona's seniority. Use the account name liberally — that's the personalization. No marketing speak. No "transformational." Direct, plain English, calibrated to the audience.
Step 4: Generate the Single-File HTML
Produce ONE .html file containing:
- Doctype + meta tags (title, description, viewport, OG tags for link previews)
- Inline
<style>block with all CSS — no external stylesheet - Semantic HTML5 sectioning
- Web-safe font stack with optional Google Fonts via
<link>if user wants - Mobile-responsive via media queries
- One primary brand color used 3-4 places (CTA button, accent line, hero background tint)
- Accessible: alt text on images, contrast ratios, focus states on the button
What ships with it
2 files 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.
- 3d ago First seen · 104 lines · 77 tokens per session scan A 90aba4884eed
microsite is a skill published in the GitHub repository GTMify/aigtm (24 stars, last pushed 25d ago), licensed MIT. It adds 77 tokens to every session and 1,194 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-08-30.
Other skills, from other repositories
npm-downloads-to-leads
Takes a list of npm package names (yours or competitors'), fetches 12 weeks of daily download data from the npm API, computes a breakout velocity score per package to identify hockey-stick growth, fetches maintainer profiles from the npm registry and GitHub API, and outputs a ranked lead brief for each breakout…
graphic-ebook
Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF. 3–10 pages, 9 style presets, 11 page layout types. Trigger when user says "create an ebook", "design a lead magnet", "make a PDF guide", "build a gated content piece", "write a B2B ebook", "design a white paper", "create a…
map-your-market
Given a product description, category keywords, or competitor names (any combination), searches Reddit, Hacker News, GitHub Issues, G2, and Google Trends for the real pains your market experiences, then synthesizes everything into a positioning framework showing who your ICP is, what they say out loud, and exactly how…
product-update-logger
Tell the skill what your product shipped. It writes a polished dated entry to a living docs/changelog.md and produces a ready-to-use content package: tweet thread, LinkedIn post, email snippet, and one-liner.
producthunt-launch-kit
Use when the user asks to prepare a Product Hunt launch or generate Product Hunt listing assets. Generates tagline variants under 60 chars, a 500-char description, a maker comment, launch-day tweet thread, LinkedIn post, and a 4-email launch sequence.
outreach-sequence-builder
Takes a buying signal and generates a personalized multi-channel outreach sequence across email, LinkedIn, and phone. Outputs 4-6 ready-to-send touchpoints over 10-14 days. Optionally drafts email touchpoints via Composio Gmail. Use when asked to write an outreach sequence, build a sales cadence, create a follow-up…