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 MartinOlivero/saas-builder --skill technical-seogit clone --depth 1 https://github.com/MartinOlivero/saas-builderWrote 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/martinolivero/saas-builder/technical-seo)<a href="https://agentmods.dev/skills/martinolivero/saas-builder/technical-seo"><img src="https://agentmods.dev/badge/skills/martinolivero/saas-builder/technical-seo/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/martinolivero/saas-builder/technical-seo"><img src="https://agentmods.dev/badge/skills/martinolivero/saas-builder/technical-seo.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.00135 | $0.00933 |
| Opus 5 | $0.00068 | $0.00466 |
| Sonnet 5 | $0.00027 | $0.00187 |
| Haiku 4.5 | $0.00014 | $0.00093 |
Grade A, and why
technical-seo 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 8d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical SEO
This skill makes a SaaS findable by Google and shareable on social — and fixes the specific trap of a Vite SPA serving near-empty HTML that crawlers can't read.
Analogy: an SPA is a book with a blank cover and blank first page until you open it and read aloud. Search crawlers and social bots only glance at the cover — if it's blank, they walk away. SEO here is printing a real cover (server-rendered head tags) so they see what the book is about.
The SPA problem (state it upfront)
A Vite SPA serves near-empty HTML; content and meta tags appear only after JS runs. Social crawlers (WhatsApp, Twitter, LinkedIn) don't run JS at all, and Googlebot does so unreliably. So SEO tags must be injected server-side or prerendered — client-only react-helmet alone won't show a preview on WhatsApp.
Discovery (max 3 questions, only if unknown)
- Which pages need SEO — public marketing/landing/pricing, or also app routes?
- Is the broken thing indexing (Google) or social previews (no image on share)?
- Can you prerender marketing routes to static HTML, or must it stay a pure SPA?
Step 1 — Per-page head tags
Use react-helmet-async to set per route: unique <title>, <meta name="description">, a canonical link, and OpenGraph + Twitter Card tags:
og:title,og:description,og:image(1200×630),og:url,twitter:card=summary_large_image.- Always absolute URLs in
og:image/canonical (relative URLs break previews). - Set
<html lang>and one canonical per page to avoid duplicate-content issues.
Step 2 — Make crawlers actually see them (the high-impact fix)
- Marketing/landing routes → prerender to static HTML with
vite-ssg(or React SSR). Crawlers get real content + OG tags in the initial response. This is the single highest-impact change. - Pure CSR SPA, OG tags only → the "OG proxy" pattern: a Vercel function +
vercel.jsonrewrite that detects social/bot user-agents and serves HTML with the correct meta injected.
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.
- 8d ago First seen · 59 lines · 135 tokens per session scan A 28398576d945
technical-seo is a skill published in the GitHub repository MartinOlivero/saas-builder (2 stars, last pushed 20d ago), licensed MIT. It adds 135 tokens to every session and 933 once invoked, about $0.0007 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
architecture-paradigm-microkernel
Applies microkernel architecture with minimal core and plugin extensibility. Use when building platforms where third parties extend core functionality.
plan
Use when a task needs structured planning before implementation. Supports --delegate and round=N[,M].
preplan
Use when a problem needs clarification and agreement before planning begins. Supports --deep and --delegate.
pathfind
Use when you have problems but don't know what to build.
ralph
Use when implementing a plan or executing a prompt that requires verified completion.
analyze
Use when deep investigation is needed — project structure, requirement gaps, or root cause diagnosis. Supports --delegate.