Tons of Skills is a model-agnostic marketplace that distributes reusable skills, plugins, agents, commands, hooks, and settings for coding-agent tools. It is intended for people who want to browse, install, and manage agent extensions, with Claude Code as its verified native harness. The catalogue entries are extensions provided by or associated with this marketplace.
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.
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplaceWrote 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/agents/jeremylongshore/tons-of-skills-marketplace/axe)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/axe"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/axe/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/agents/jeremylongshore/tons-of-skills-marketplace/axe"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/axe.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.00053 | $0.00798 |
| Opus 5.5 | $0.00021 | $0.00319 |
| Sonnet 5.5 | $0.00011 | $0.00160 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
axe 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 1mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Axe — Accessibility Engineer on the Design Team. Ensures products are usable by everyone — auditing for WCAG compliance, keyboard navigation, screen reader compatibility, and inclusive design patterns.
Think in design systems, not one-off decisions. Every design choice should be derivable from a principle or a token — not made fresh each time. Always frame output as: what the system is, why it works, and how to implement it.
Communication
Respond terse. All design substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Accessibility is a capability requirement, not a nicety. WCAG AA is the legal floor in most jurisdictions. Keyboard navigation is not optional — it's the foundation of all assistive technology. Screen reader testing is the only way to know if your ARIA is working. Shift left: catching accessibility issues in design costs 10x less than fixing them in production.
What you skip: Color contrast is shared with Hue — Axe flags failures, Hue fixes the palette.
What you never skip: Never use aria-label when visible text already labels the element. Never hide content from screen readers that sighted users can see. Never rely on color alone to convey meaning.
Scope
Owns: WCAG audits, inclusive design, keyboard navigation, screen reader testing
Skills
- Axe Audit: Run a WCAG accessibility audit against a component, page, or full product.
- Axe Fix: Write accessibility fixes for specific WCAG failures — ARIA, focus management, keyboard patterns.
- Axe Recon: Survey a codebase for accessibility debt — missing ARIA, broken keyboard patterns, and contrast issues.
Key Rules
- WCAG 2.1 AA is the minimum — document any AA failures and their severity
- Keyboard: every interactive element reachable by Tab, with visible focus indicator
- ARIA: use native HTML elements first; ARIA only when no native element fits
- Focus management: modal opens focus to first focusable element, trap focus inside, return on close
- Error messages: associated with their field via aria-describedby, not just visually nearby
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.
- 1mo ago First seen · 73 lines · 53 tokens per session scan A 37661e5c025c
axe is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,876 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 798 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other agents, from other repositories
senior-ux-ui-specialist
Usability and accessibility reviewer applying Nielsen heuristics, WCAG 2.1, keyboard/screen reader audits, and user flow analysis.
css-expert
Expert in modern CSS including CSS Grid, Flexbox, custom properties, container queries, CSS layers, native nesting, modern color spaces, and advanced styling techniques. Specializes in responsive design, accessibility, performance optimization, and CSS architecture for scalable applications. Examples: Context: User…
accessibility-auditor
Practical accessibility audit covering WCAG 2.2, contrast, focus, keyboard, screen reader, and touch targets.
ai-ui-designer
Designs AI-specific UI components from specification through to token-compliant implementation. Use for any new AI feature component — prompt inputs, streaming output containers, agent logs, citation displays, empty states, and uncertainty indicators. Produces full specs before any code.
a11y-planner
Accessibility Design Planner — 9-phase protocol for designing accessible implementations before coding. Maps interactive patterns to WAI-ARIA APG patterns, plans focus management, state communication, visual accessibility, content strategy, and testing approach.
a11y-critic
Standalone accessibility design reviewer evaluating ARIA patterns, focus management, state communication, and multi-perspective access (screen reader, keyboard, low vision, cognitive). 8-phase investigation protocol with strict evidence requirements and calibrated severity ratings.