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 skills add AmadeusITGroup/otter --skill a11y-axe-playwrightgit clone --depth 1 https://github.com/AmadeusITGroup/otterWrote 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/amadeusitgroup/otter/a11y-axe-playwright)<a href="https://agentmods.dev/skills/amadeusitgroup/otter/a11y-axe-playwright"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/a11y-axe-playwright/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/skills/amadeusitgroup/otter/a11y-axe-playwright"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/a11y-axe-playwright.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 121 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00040 | $0.00966 |
| Opus 5 | $0.00020 | $0.00483 |
| Sonnet 5 | $0.00008 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
a11y-axe-playwright 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 9d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Axe Scans with Playwright
Setup
Install the dependency:
yarn add -D @axe-core/playwright
Import in test files:
import AxeBuilder from '@axe-core/playwright';
Tag Selection
| Scenario | Tags |
|---|---|
| Existing component or page | ['wcag2a', 'wcag2aa', 'wcag21aa'] |
| New component (WCAG 2.2) | ['wcag2a', 'wcag2aa', 'wcag21aa', 'wcag22aa'] |
Never omit tags — an untagged scan runs all rules including experimental ones and produces noise.
Scoping
Always scope scans to the component under test using .include(). Avoid scanning the full page when testing a single component.
const results = await new AxeBuilder({ page })
.include('#my-component-selector')
.withTags(['wcag2a', 'wcag2aa', 'wcag21aa'])
.analyze();
For full page audits, omit .include():
const results = await new AxeBuilder({ page })
.withTags(['wcag2a', 'wcag2aa', 'wcag21aa'])
.analyze();
When to Run Axe Scans
Run an axe scan at each significant page state transition:
- Initial page load
- After form submission
- After navigation to a new page/view
- After modal/dialog opens
- After dynamic content loads (search results, filtered lists)
Test Pattern
import { test, expect } from '@playwright/test';
import AxeBuilder from '@axe-core/playwright';
test.describe('MyComponent accessibility @a11y', () => {
test('should have no WCAG 2.1 AA violations', async ({ page }) => {
await page.goto('/my-component-route');
const results = await new AxeBuilder({ page })
.include('#my-component-selector')
.withTags(['wcag2a', 'wcag2aa', 'wcag21aa'])
.analyze();
expect(results.violations).toEqual([]);
});
});
Interpreting Violations
Each violation in results.violations contains:
id— axe rule id (e.g.color-contrast,label,aria-required-attr)impact—critical,serious,moderate, orminordescription— what the rule checksnodes— list of affected elements withhtmlsnippet andfailureSummary
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.
- 9d ago First seen · 133 lines · 40 tokens per session scan A 817e5a015a8b
a11y-axe-playwright is a skill published in the GitHub repository AmadeusITGroup/otter (58 stars, last pushed today), licensed BSD-3-Clause. It adds 40 tokens to every session and 966 once invoked, about $0.0002 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
aperture_lab_reviewer
Review Aperture Lab F-Stop offline review prompts and return JSON-only findings about title, summary, status, intentFrame, toolFamily, and consequence. Use when acting as the reviewer model inside the Aperture Lab F-Stop loop; do not edit code and do not return prose outside the required JSON.
figma-fetch
Extract frame/component structure and all visible text from a Figma design URL. Use whenever a prompt or a fetched issue contains a figma.com/design or figma.com/file link.
relational-database-design
Designs or reviews a relational database schema for a given domain. Covers table structure, normalization, indexes, constraints, and migration strategy. Invoked when the user asks to design a schema, review a database structure, or optimize a data model.
code-quality-analysis
Analyze Angular / Cumulocity Web SDK code for anti-patterns, bugs, and quality issues. Use when reviewing components, services, or modules for code quality, maintainability, performance, and correctness. Covers TypeScript best practices, Angular idioms, C8Y SDK usage patterns, and project-specific conventions.…
igniteui-angular-figma-to-app
Translate Figma app screens designed using the Indigo.Design UI Kits into production Angular applications with Ignite UI for Angular. The Indigo.Design UI Kits are Figma component libraries available in four design-system variants — Material, Fluent, Bootstrap, and Indigo — each with light and dark themes. Designers…
igniteui-angular-generate-from-image-design
Implement Angular application views from design images using Ignite UI Angular components. Uses MCP servers (igniteui-cli, igniteui-theming, angular-cli) to discover components, generate themes, and follow best practices. Triggers when the user provides a design image (screenshot, mockup, wireframe) and wants it built…