audit-website

audit-website is a skill for Claude Code, Codex from AlekseiUL/sprut-agent-kit. It costs 89 tokens per session (958 once invoked), scanned A, original, MIT.

A workflow for auditing websites and landing pages across search visibility, loading speed, security, content, and accessibility. SEO, or search engine optimisation, covers changes that help search engines understand and rank a site.

In plain words
What is it for?
Use it to inspect a website's page structure, metadata, images, performance, HTTPS and security headers, accessibility, and related SEO files.
Why use it?
It turns a broad website check into a list of specific problems and recommended fixes.

Skill for Claude CodeCodex

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

Good fit Use it to inspect a website's page structure, metadata, images, performance, HTTPS and security headers, accessibility, and related SEO files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alekseiul/sprut-agent-kit/audit-website
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 AlekseiUL/sprut-agent-kit --skill audit-website
Clone the repo
git clone --depth 1 https://github.com/AlekseiUL/sprut-agent-kit

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/alekseiul/sprut-agent-kit/audit-website.svg)](https://agentmods.dev/skills/alekseiul/sprut-agent-kit/audit-website)
Your own site
<a href="https://agentmods.dev/skills/alekseiul/sprut-agent-kit/audit-website"><img src="https://agentmods.dev/badge/skills/alekseiul/sprut-agent-kit/audit-website.svg" alt="Measured on agentmods" height="20"></a>
Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 958 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.00089 $0.00958
Opus 5 $0.00044 $0.00479
Sonnet 5 $0.00018 $0.00192
Haiku 4.5 $0.00009 $0.00096

Measured 7d ago against content hash addbfc066ec1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

audit-website 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 7d 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/SKILL.md · 114 lines

How it starts

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

Аудит веб-сайтов

Комплексная проверка сайта по ключевым категориям с конкретными рекомендациями.

Процесс

1. Сбор данных

Для каждого URL выполни:

# Основная страница
web_fetch URL → анализ контента

# Через браузер (для JS-heavy сайтов)
browser action=open targetUrl=URL
browser action=snapshot → структура DOM

Если доступен squirrel CLI:

squirrel audit URL --format llm

2. Категории проверки

SEO (критично)
  • Title: 30-60 символов, содержит ключевое слово
  • Meta description: 120-160 символов, содержит CTA
  • H1: один на страницу, содержит ключевое слово
  • Иерархия заголовков: H1 → H2 → H3, без пропусков
  • Canonical URL установлен
  • Open Graph теги (og:title, og:description, og:image)
  • Alt-текст у всех изображений
  • URL структура: короткий, с дефисами, без параметров
  • Robots.txt и sitemap.xml
  • Внутренняя перелинковка
Производительность
  • Время загрузки (web_fetch tookMs)
  • Размер страницы (rawLength)
  • Изображения оптимизированы (WebP/AVIF, lazy loading)
  • Минификация CSS/JS
  • Кеширование (Cache-Control headers)
  • Нет блокирующих ресурсов в head
Безопасность
  • HTTPS
  • Security headers (CSP, X-Frame-Options, HSTS)
  • Нет утечек в исходниках (ключи, токены, внутренние URL)
  • Формы защищены (CSRF)
Контент и UX
  • Чёткий value proposition в первом экране
  • CTA виден без скролла
  • Мобильная адаптация
  • Читаемость (размер шрифта, контраст)
  • Нет битых ссылок
  • Контактная информация
Доступность
  • Alt-текст изображений
  • Семантическая разметка (nav, main, footer)
  • Контраст текста
  • Фокус-индикаторы для навигации
  • ARIA-метки где нужно
Schema.org
  • Тип разметки соответствует странице (Organization, Product, Article)
  • Хлебные крошки
  • FAQ schema если есть вопросы-ответы

3. Формат отчёта

# Аудит: [URL]
**Дата:** YYYY-MM-DD
**Общий балл:** X/100

## 🔴 Критичные (исправить немедленно)
- [проблема] → [конкретное решение]

## 🟡 Важные (исправить в ближайшее время)
- [проблема] → [конкретное решение]

## 🟢 Рекомендации (при возможности)
- [проблема] → [конкретное решение]

## ✅ Что хорошо
- [что работает правильно]

Read the full file on GitHub · 114 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. 7d ago First seen · 114 lines · 89 tokens per session scan A addbfc066ec1

Subscribe to this mod's changes

audit-website is a skill published in the GitHub repository AlekseiUL/sprut-agent-kit (63 stars, last pushed 3mo ago), licensed MIT. It adds 89 tokens to every session and 958 once invoked, about $0.0004 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-30.

Related

Other skills, from other repositories

cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…

sangrokjung/claude-forge · 183 tokens

frontend-code-review

Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.

sangrokjung/claude-forge · 42 tokens

panel-app-creator

Create or update the Panel UI component of a complete schema v2 NextClaw Mini App or an explicitly loose local Panel. Use after nextclaw-app-creator selects Panel-only or Panel + Service, or for right-side UI, Service Actions, Agent-powered panels, React/Vite panels, and App bridge capability questions.

Peiiii/nextclaw · 70 tokens

gemigo-cli

Use when the user wants to publish an already-built static website or front-end app through GemiGo, such as a Vite/React/Vue static build, plain HTML/CSS/JS page, landing page, demo, docs site, or small browser app, and get a hosted public URL.

Peiiii/nextclaw · 65 tokens

impeccable

Use when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable references and an optional upstream detector CLI.

Peiiii/nextclaw · 47 tokens

ui-ux-pro-max

Use when the user wants professional UI/UX design guidance, design-system generation, UX review, or stack-specific frontend guidance through a bundled local UI/UX Pro Max dataset and Python search runtime.

Peiiii/nextclaw · 45 tokens