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 solo-super/marketplace --skill seo-preflightgit clone --depth 1 https://github.com/solo-super/marketplaceWrote 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/solo-super/marketplace/seo-preflight)<a href="https://agentmods.dev/skills/solo-super/marketplace/seo-preflight"><img src="https://agentmods.dev/badge/skills/solo-super/marketplace/seo-preflight/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/solo-super/marketplace/seo-preflight"><img src="https://agentmods.dev/badge/skills/solo-super/marketplace/seo-preflight.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.00034 | $0.03391 |
| Opus 5 | $0.00017 | $0.01695 |
| Sonnet 5 | $0.00007 | $0.00678 |
| Haiku 4.5 | $0.00003 | $0.00339 |
Grade A, and why
seo-preflight 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 12d 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 — 398 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<quick_start>
- Read the HTML file (usually index.html)
- Audit existing meta tags against requirements
- Add missing SEO, OG, Twitter, and JSON-LD tags
- Validate OG image requirements
- Generate the OG image (1200×630) with your image tool of choice if one's needed
- Output checklist with pass/fail status </quick_start>
<meta_tag_requirements>
Core SEO Tags (Required)
| Tag | Purpose | Optimal Length |
|---|---|---|
<title> |
Page title, search results headline | 50-60 chars |
<meta name="description"> |
Search result snippet | 150-160 chars |
<meta name="robots"> |
Crawl instructions | index, follow |
<link rel="canonical"> |
Prevent duplicate content | Full URL |
Optional SEO Tags
| Tag | Purpose |
|---|---|
<meta name="keywords"> |
Topic hints (low SEO value, still useful) |
<meta name="author"> |
Content attribution |
<html lang="en"> |
Language declaration |
</meta_tag_requirements>
<open_graph_requirements>
Open Graph Tags (Required for Social Sharing)
| Tag | Purpose | Requirements |
|---|---|---|
og:type |
Content type | website, article, profile |
og:url |
Canonical URL | Full URL with https |
og:title |
Social headline | 50-60 chars optimal |
og:description |
Social preview text | 100-150 chars |
og:image |
Preview image | Full URL, 1200×630px |
og:image:width |
Image width | 1200 |
og:image:height |
Image height | 630 |
og:site_name |
Site/brand name | Short name |
og:locale |
Language/region | en_US, en_GB, etc. |
Example
<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/">
<meta property="og:title" content="Site Name — Compelling Tagline Here">
<meta property="og:description" content="Clear value proposition in 100-150 characters.">
<meta property="og:image" content="https://example.com/og-image.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:site_name" content="Site Name">
<meta property="og:locale" content="en_US">
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.
- 12d ago First seen · 398 lines · 34 tokens per session scan A 681e149c54dc
seo-preflight is a skill published in the GitHub repository solo-super/marketplace (2 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 3,391 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…