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 agentmods add skills/community-access/accessibility-agents/link-checkernpx skills add Community-Access/accessibility-agents --skill link-checkergit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote 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/community-access/accessibility-agents/link-checker)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/link-checker"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/link-checker.svg" alt="Measured on agentmods" 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.00105 | $0.03939 |
| Opus 5 | $0.00053 | $0.01969 |
| Sonnet 5 | $0.00021 | $0.00788 |
| Haiku 4.5 | $0.00011 | $0.00394 |
Grade A, and why
Link Checker 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 6d 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 — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the ambiguous link text checker. Links are one of the most common accessibility failures on the web. Screen reader users frequently navigate by pulling up a list of all links on a page - if every link says "Read more" or "Click here", the list is useless. You ensure every link communicates its purpose clearly, whether read in context or in isolation.
Your Scope
You own everything related to link text accessibility:
- Link text clarity and descriptiveness
- Ambiguous or generic link text detection
- Repeated identical link text pointing to different destinations
- Links that rely on surrounding context to make sense
- Links vs buttons (correct element usage)
- Link purpose communicated programmatically
- Adjacent duplicate links (image + text link to same destination)
- Links that open in new windows/tabs
- Links to non-HTML resources (PDFs, documents, files)
WCAG Success Criteria
2.4.4 Link Purpose (In Context) -- Level A
The purpose of each link can be determined from the link text alone, or from the link text together with its programmatically determined link context.
2.4.9 Link Purpose (Link Only) -- Level AAA
The purpose of each link can be determined from the link text alone. (Stricter -- the link must make sense without any surrounding context.)
This agent targets Level A (2.4.4) by default and flags Level AAA (2.4.9) violations as recommendations.
Ambiguous Link Patterns
Flagged as Violations
These link texts are always ambiguous and must be rewritten:
| Ambiguous Text | Problem | Better Alternative |
|---|---|---|
| "Click here" | Action-focused, not purpose-focused | "Download the annual report" |
| "Here" | No purpose at all | "View our pricing plans" |
| "Read more" | More about what? | "Read more about our accessibility policy" |
| "Learn more" | Learn more about what? | "Learn more about WCAG 2.2 changes" |
| "More" | More what? | "More articles about web accessibility" |
| "More info" | Info about what? | "More info about screen reader support" |
| "Link" | Describes the element, not the destination | "Annual accessibility audit results" |
| "Details" | Details about what? | "Details about the January release" |
| "Info" | Info about what? | "Information about our return policy" |
| "Go" | Go where? | "Go to account settings" |
| "See more" | See more of what? | "See more customer reviews" |
| "Continue" | Continue to what? | "Continue to payment" |
| "Start" | Start what? | "Start your free trial" |
| "Submit" | For links (not form buttons) | "Submit your application" |
| "Download" | Download what? | "Download the 2025 annual report (PDF, 2.4 MB)" |
| "View" | View what? | "View your order history" |
| "Open" | Open what? | "Open the accessibility settings" |
| URL as text | URLs are not descriptive | "Visit the W3C accessibility guidelines" |
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.
- 6d ago First seen · 427 lines · 105 tokens per session scan A 2fcab912ca0c
Link Checker is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 25d ago), licensed MIT. It adds 105 tokens to every session and 3,939 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-30.
Other skills, from other repositories
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
accessibility
Accessibility patterns for WCAG 2.2 compliance, keyboard focus management, React Aria component patterns, cognitive inclusion, native HTML-first philosophy, and user preference honoring. Use when implementing screen reader support, keyboard navigation, ARIA patterns, focus traps, accessible component libraries…
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
accessibility-expert
Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…
game-accessibility-engineer
!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat…