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 calm-north/seojuice-claude-plugin --skill site-healthgit clone --depth 1 https://github.com/calm-north/seojuice-claude-pluginWrote 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/calm-north/seojuice-claude-plugin/site-health)<a href="https://agentmods.dev/skills/calm-north/seojuice-claude-plugin/site-health"><img src="https://agentmods.dev/badge/skills/calm-north/seojuice-claude-plugin/site-health/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/calm-north/seojuice-claude-plugin/site-health"><img src="https://agentmods.dev/badge/skills/calm-north/seojuice-claude-plugin/site-health.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.00063 | $0.01013 |
| Opus 5 | $0.00032 | $0.00507 |
| Sonnet 5 | $0.00013 | $0.00203 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
site-health 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Site Health Check
Analyze site structure, internal linking, performance metrics, accessibility, and content decay.
Instructions
-
Resolve the domain. If
$ARGUMENTSis provided, use it as the domain. If not, calllist_websitesand ask the user which site to analyze. -
Fetch site topology. Call
get_site_topologywith the domain. This returns orphan pages, link depth distribution, most linked pages, and average links per page. -
Fetch page speed for the homepage. Call
get_pagespeedwith:domain: the target domainurl: the homepage URL (typicallyhttps://[domain]/)
-
Optionally fetch speed for hub pages. If topology reveals pages with many incoming links, check their speed with
get_pagespeedfor 1-2 of the most linked pages. -
Fetch accessibility issues. Call
list_accessibility_issueswith:domain: the target domainpage_size: 10
-
Fetch content decay alerts. Call
list_content_decaywith:domain: the target domainis_active: "true"page_size: 10
-
Synthesize into a technical health report.
Output Format
Technical Health Report: [domain]
Site Structure Overview
- Total Pages: [count]
- Total Internal Links: [count]
- Average Links Per Page: [avg]
- Orphan Pages: [count]
Link Depth Distribution
| Depth | Pages | Assessment |
|---|---|---|
| 0 (homepage) | [count] | -- |
| 1 | [count] | Ideal for important pages |
| 2 | [count] | Good |
| 3 | [count] | Acceptable |
| 4+ | [count] | Too deep -- may not be crawled effectively |
Orphan Pages (no incoming internal links)
List up to 20 orphan page URLs.
Most Linked Pages (top internal link hubs)
| URL | Incoming Links |
|---|---|
| ... | ... |
Core Web Vitals: Homepage
| Metric | Value | Rating |
|---|---|---|
| LCP | [value]ms | Good / Needs Improvement / Poor |
| CLS | [value] | Good / Needs Improvement / Poor |
| INP | [value]ms | Good / Needs Improvement / Poor |
| FCP | [value]ms | Good / Needs Improvement / Poor |
| TTFB | [value]ms | Good / Needs Improvement / Poor |
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 · 113 lines · 63 tokens per session scan A af07cdcea9de
site-health is a skill published in the GitHub repository calm-north/seojuice-claude-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 1,013 once invoked, about $0.0003 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
content-amplifier
Use when the user asks to "amplify influencer content with paid media", "set up whitelisting or Spark Ads", "decide which posts to boost", "repurpose influencer content", "turn one video into multiple ads", or "build a UGC asset library"; produces (paid mode) a content-selection scorecard, a paid amplification…
email-sequence-designer
Use when the user asks to "design a welcome flow", "set up an abandoned-cart sequence", "build a light re-engagement branch inside a lifecycle flow", or "plan a cold-outbound sequence"; produces general lifecycle automation flows (welcome, cart, browse-abandon, post-purchase, in-flow re-engagement, B2B cold outbound)…
reactivation-specialist
Use when the user asks to "build a win-back campaign", "re-engage lapsed subscribers", "run a re-permission / re-consent sweep", or "sunset my dead list"; produces a closed-loop reactivation program — a lapsed-cohort definition, a staged offer ladder, a re-consent (re-permission) capture step, and a sunset-confirm /…
campaign-planner
Use when the user asks to "plan an influencer campaign", "build a campaign blueprint", "track or close a creator campaign", or "record a late campaign correction"; produces the plan and, when requested, a non-canonical evidence tracker with scoped identity, publication, reconciliation, close, and reopen receipts. Not…
product-feed-optimizer
Use when the user asks to "optimize my Shopping feed", "fix product disapprovals", "improve product titles/attributes", or "build feed-driven PMax asset groups"; audits and rewrites the Shopping/Performance Max product feed — title/description patterns, required and recommended attributes, GTIN/availability/price…
attribution-reconciler
Use when platform-reported conversions disagree with GA4/ecommerce, when you suspect Meta and Google are double-counting the same sales, or for a standing (monthly) reconciliation workbook that de-dups stacked credit against an order-ID truth set, normalizes attribution windows and currency, compares attribution…