accesslint-scan

accesslint-scan is a skill for Claude Code from Ghosteken/agent-harness. It costs 32 tokens per session (490 once invoked), scanned A, a copy of accesslint-scan, MIT.

A guide for auditing a live web page for accessibility problems, which can make a site difficult for people with disabilities to use.

In plain words
What is it for?
Use it to check a page against WCAG accessibility rules, identify affected elements with selectors, record evidence, and produce fixes without editing the page.
Why use it?
It locates each reported issue precisely and provides evidence and a fix list, so developers can work out what needs changing without guessing.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the agent-harness plugin — 173 skills, 11 commands, 12 agents shipped together

Good fit Use it to check a page against WCAG accessibility rules, identify affected elements with selectors, record evidence, and produce fixes without editing the page.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ghosteken/agent-harness/accesslint-scan
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 Ghosteken/agent-harness --skill accesslint-scan
Clone the repo
git clone --depth 1 https://github.com/Ghosteken/agent-harness

Made for: Claude Code.

Or install agent-harness, the plugin that ships this one along with the rest of its 173 skills, 11 commands, 12 agents.

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 accesslint-scan

README.md
[![agentmods](https://agentmods.dev/badge/skills/ghosteken/agent-harness/accesslint-scan.svg)](https://agentmods.dev/skills/ghosteken/agent-harness/accesslint-scan)
Your own site
<a href="https://agentmods.dev/skills/ghosteken/agent-harness/accesslint-scan"><img src="https://agentmods.dev/badge/skills/ghosteken/agent-harness/accesslint-scan.svg" alt="Measured on agentmods" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 490 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 100% copy Near-identical to another mod 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.00032 $0.00490
Opus 5 $0.00016 $0.00245
Sonnet 5 $0.00006 $0.00098
Haiku 4.5 $0.00003 $0.00049

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

Security

Grade A, and why

accesslint-scan 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.

Origin

This is a copy

100% identical to accesslint-scan — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

archive/skills-community/accesslint-scan/SKILL.md · 48 lines

What it actually says

Audit a live page and report what's broken and where. Locate; don't fix. If no URL in $ARGUMENTS, ask for one.

When to Use

  • Use this skill when the task matches this description: Audit a live page for accessibility issues, locate each WCAG violation precisely, and return a selector-grounded fix worklist without editing.

1. Audit

PORT=$(npx -y @accesslint/chrome@latest ensure | node -e 'process.stdin.on("data",d=>process.stdout.write(""+JSON.parse(d).port))')
npx -y @accesslint/cli@latest "<url>" --port "$PORT" --format json

Flags as needed: --selector, --wait-for "<selector>", --include-aaa, --disable <rules>.

2. Report

Counts by impact, then one entry per violation:

  • where — selector verbatim + file:line (symbol) if source is present — never fabricate. If no violation has source, note "source mapping unavailable — located by selector only".
  • evidence — contrast ratio, missing attribute, empty name
  • fix — mechanical change or NEEDS HUMAN

Don't edit. For fixes: apply mechanical ones then re-run to verify; for bulk work hand off to accesslint:audit.

3. Tear down

npx -y @accesslint/chrome@latest stop --all  # skip if ensure reported "managed":false

Gotchas

  • ensure always determines the port — never hardcode 9222.
  • CLI exit 2 = bad URL or page never loaded; check the dev server.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
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 · 48 lines · 32 tokens per session scan A ed6f7bce4d22

Subscribe to this mod's changes

accesslint-scan is a skill published in the GitHub repository Ghosteken/agent-harness (2 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 490 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to accesslint-scan, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

web-clone

URL-driven website cloning with visual + functional verification.

IAPro-Community/Orquestrador-Maestro · 13 tokens

skill-saas-factory

Build, refactor, review, or plan SaaS products with React/Vite, dashboards, admin panels, Supabase, payments, subscriptions, tenant limits, webhooks, security, infrastructure, and production readiness. Use as the top-level SaaS construction skill when work may need routing to payment, RLS, dashboard, limits, security…

IAPro-Community/Orquestrador-Maestro · 80 tokens

skill-frontend-ux-guardrails

Apply frontend UX quality gates for SaaS dashboards, product screens, modals, tables, forms, responsive layouts, overflow fixes, accessibility, visual validation, spelling, and reduction of UI rework.

IAPro-Community/Orquestrador-Maestro · 49 tokens

skill-modern-ui-patterns

Use for professional SaaS UI implementation and refinement in React, TypeScript, Tailwind, dashboards, admin panels, tables, forms, settings, billing, onboarding, responsive layouts, component states, and design-system consistency.

IAPro-Community/Orquestrador-Maestro · 50 tokens

skill-open-design-ui

Apply open-design product UI workflow for premium visual redesigns, dashboards, landing pages, design tokens, component libraries, responsive product screens, visual QA, anti-generic styling, and professional frontend delivery.

IAPro-Community/Orquestrador-Maestro · 45 tokens

skill-impeccable

Orquestra melhorias de frontend inspiradas no Impeccable a partir de pedidos conversacionais de design, UX, acessibilidade, responsividade, tipografia, layout, cor, motion, clareza, hardening e polish.

IAPro-Community/Orquestrador-Maestro · 53 tokens