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 jschulte/claude-plugins --skill health-audit-seogit clone --depth 1 https://github.com/jschulte/claude-pluginsWrote 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/jschulte/claude-plugins/health-audit-seo)<a href="https://agentmods.dev/skills/jschulte/claude-plugins/health-audit-seo"><img src="https://agentmods.dev/badge/skills/jschulte/claude-plugins/health-audit-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/jschulte/claude-plugins/health-audit-seo"><img src="https://agentmods.dev/badge/skills/jschulte/claude-plugins/health-audit-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.00099 | $0.08159 |
| Opus 5.5 | $0.00040 | $0.03264 |
| Sonnet 5.5 | $0.00020 | $0.01632 |
| Haiku 4.5 | $0.00010 | $0.00816 |
Grade A, and why
health-audit-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 24d 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 — 563 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO & Web Presence Health Audit Skill
Use this skill when the user wants a deep audit of a web application's discoverability, search engine optimization, social sharing quality, structured data, crawlability, Core Web Vitals signals, or overall public-facing technical foundation. The skill may audit the whole public surface or focus on a user-specified route family, content type, metadata concern, crawlability issue, or sharing surface. This is NOT a code quality or architecture audit — /health-audit does that. This is NOT a UX polish audit — /health-audit-ux does that. This skill is about how search engines see the site, how social platforms render shared links, and whether the technical SEO foundation is solid.
Mission
Perform a rigorous, evidence-backed SEO and web presence audit from two perspectives: how Googlebot (and other crawlers) experience the site, and how a person sees a link shared on social media. Evaluate the technical foundation that determines discoverability: meta tags, structured data, crawlability, rendering strategy, Core Web Vitals signals, image optimization, URL architecture, resource loading, accessibility signals that affect SEO, and internationalization.
This audit only applies to web applications with public-facing pages. If the project is an internal tool, API-only service, native mobile app, or has no publicly accessible HTML pages, say so and skip the audit.
Do not guess at search rankings, traffic numbers, keyword competitiveness, or SERP position. Do not produce vague "SEO best practices" fluff. Do not invent problems. Audit the technical foundation only — the things visible in the source code that directly affect how crawlers index, how social platforms render, and how real users experience page load.
Focus Prompt Support
This skill can take an optional prompt that describes the SEO/web-presence area to focus on.
Examples:
- "Focus on Open Graph tags"
- "Review crawlability for docs pages"
- "Audit blog post metadata and structured data"
- "Look at product pages on mobile performance"
- "Review internationalization and canonicals"
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.
- 24d ago First seen · 563 lines · 99 tokens per session scan A 24a8ebfd9cf1
health-audit-seo is a skill published in the GitHub repository jschulte/claude-plugins (0 stars, last pushed 25d ago), licensed MIT. It adds 99 tokens to every session and 8,159 once invoked, about $0.0004 per session on Opus 5.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-10-12.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…