audit-website-insights

audit-website-insights is a skill for Claude Code, Codex from microlinkhq/mcp. It costs 92 tokens per session (784 once invoked), scanned A, original, MIT.

A website auditing skill that checks a public URL with Lighthouse, a website quality checker, and Wappalyzer, which identifies the technologies a site uses.

In plain words
What is it for?
Use it to inspect Lighthouse scores, Core Web Vitals, SEO, accessibility, best practices, progressive web app support, and the site's technology stack.
Why use it?
It brings performance, search visibility, accessibility, and technology information into one audit.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to inspect Lighthouse scores, Core Web Vitals, SEO, accessibility, best practices, progressive web app support, and the site's technology stack.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microlinkhq/mcp/audit-website-insights
Install

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.

Any agent
npx skills add microlinkhq/mcp --skill audit-website-insights
Clone the repo
git clone --depth 1 https://github.com/microlinkhq/mcp

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for audit-website-insights

README.md
[![agentmods](https://agentmods.dev/badge/skills/microlinkhq/mcp/audit-website-insights/github.svg)](https://agentmods.dev/skills/microlinkhq/mcp/audit-website-insights)
Your own site
<a href="https://agentmods.dev/skills/microlinkhq/mcp/audit-website-insights"><img src="https://agentmods.dev/badge/skills/microlinkhq/mcp/audit-website-insights/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.

agentmods 80×15 button for audit-website-insights

Your own site · 80×15
<a href="https://agentmods.dev/skills/microlinkhq/mcp/audit-website-insights"><img src="https://agentmods.dev/badge/skills/microlinkhq/mcp/audit-website-insights.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 784 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00092 $0.00784
Opus 5 $0.00046 $0.00392
Sonnet 5 $0.00018 $0.00157
Haiku 4.5 $0.00009 $0.00078

Measured 8d ago against content hash 4dd5722df03e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

audit-website-insights 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.

skills/audit-website-insights/SKILL.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Audit website insights

Get a Lighthouse audit and detected technology stack for a URL via microlink_insights.

Run an audit

Pass insights: true for defaults, or an insights object to configure it:

  • Lighthouse only: { "url": "...", "insights": { "lighthouse": true } }
  • Technologies only: { "url": "...", "insights": { "technologies": true } }
  • Both (default): { "url": "...", "insights": true }

Configure Lighthouse under insights.lighthouse:

  • preset: "desktop", "perf", "experimental", "lr-desktop", "lr-mobile", "full", or "default" (mobile). Use "desktop" for desktop-emulated audits.
  • onlyCategories: limit the audit to specific categories to run faster, e.g. ["performance", "accessibility"]. Valid IDs: performance, accessibility, best-practices, seo, pwa.
  • output: "json" (default), "html", or "csv".

Focused performance-only example:

{
  "url": "https://example.com",
  "insights": {
    "lighthouse": { "preset": "desktop", "onlyCategories": ["performance"] },
    "technologies": true
  }
}

Read the results

  • Category scores: microlink.data.insights.lighthouse.categories.<id>.score (0–1; multiply by 100 for the familiar 0–100 score).
  • Core Web Vitals & metrics: under microlink.data.insights.lighthouse.audits (e.g. largest-contentful-paint, cumulative-layout-shift, total-blocking-time, first-contentful-paint).
  • Tech stack: microlink.data.insights.technologies — an array of detected tools/frameworks (name + categories), e.g. React, Next.js, Cloudflare, GA.

When reporting to the user, translate scores to 0–100, call out the weakest category, and cite the specific failing audits rather than only the headline number.

Tips & gotchas

  • Slow tool: a full Lighthouse run takes many seconds. Narrow with onlyCategories and a preset to speed things up when you only need one dimension.
  • Timeouts: raise timeout (e.g. "60s") for heavy pages.
  • Fresh numbers: audits are cached — pass force: true to re-measure.
  • Combine: microlink_extract accepts insights alongside screenshot/meta, so you can grab an audit and a screenshot of the page in one request.
  • Free endpoint caps at 50 requests/day; set MICROLINK_API_KEY for more.

Read the full file on GitHub · 70 lines

Changes

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.

  1. 8d ago First seen · 70 lines · 92 tokens per session scan A 4dd5722df03e

Subscribe to this mod's changes

audit-website-insights is a skill published in the GitHub repository microlinkhq/mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 92 tokens to every session and 784 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

unity-version-split

Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).

IvanMurzak/Unity-MCP · 59 tokens

specflow-use

To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.

griddynamics/rosetta · 27 tokens

opik-diagnose

Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, then fills the gaps with list (filters, sort, a time…

comet-ml/opik-mcp · 174 tokens

qa-knowledge

To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.

griddynamics/rosetta · 32 tokens

ue-mcp-epic-routing

Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.

db-lyon/ue-mcp · 81 tokens