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-keyboard-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-keyboard-playwright)<a href="https://agentmods.dev/skills/amadeusitgroup/otter/a11y-keyboard-playwright"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/a11y-keyboard-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-keyboard-playwright"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/a11y-keyboard-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 184 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.00034 | $0.01345 |
| Opus 5 | $0.00017 | $0.00673 |
| Sonnet 5 | $0.00007 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
a11y-keyboard-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 10d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Keyboard and Focus Tests with Playwright
Keyboard-Only Variants
Replicate each E2E scenario using only keyboard navigation. Tag with @a11y.
Keyboard Navigation Patterns
| Action | Keys | Notes |
|---|---|---|
| Move to next interactive element | Tab |
Forward navigation |
| Move to previous element | Shift+Tab |
Backward navigation |
| Activate button/link | Enter |
Triggers click |
| Toggle checkbox/radio | Space |
Toggles state |
| Open dropdown | Enter or Space |
Context-dependent |
| Navigate dropdown options | Arrow Down / Arrow Up |
Within open dropdown |
| Select dropdown option | Enter |
Confirms selection |
| Close modal/dialog | Escape |
Should return focus |
| Navigate tabs | Arrow Left / Arrow Right |
Within tablist |
Example
// scenarios/add-to-cart/add-to-cart-keyboard.e2e.spec.ts
test.describe('Add to Cart - Keyboard @happy-path @a11y', () => {
test('complete flow via keyboard only', async ({ page }) => {
await actions.navigateToCatalog(page);
await keyboardActions.focusSearchAndType(page, 'laptop');
await keyboardActions.submitWithEnter(page);
await keyboardActions.tabToAndActivate(page); // first result
await keyboardActions.tabToAndActivate(page); // add-to-cart button
await checks.verifyItemInCart(page, 'Laptop');
});
});
Keyboard Actions Helpers
// actions/keyboard-actions.ts
export async function tabThroughElements(page: Page, count: number): Promise<void> {
for (let i = 0; i < count; i++) {
await page.keyboard.press('Tab');
}
}
export async function shiftTabThroughElements(page: Page, count: number): Promise<void> {
for (let i = 0; i < count; i++) {
await page.keyboard.press('Shift+Tab');
}
}
export async function closeModalViaEscape(page: Page): Promise<void> {
await page.keyboard.press('Escape');
}
Focus Management Checks
Verify that focus moves predictably after interactions.
Common Focus Expectations
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.
- 10d ago First seen · 186 lines · 34 tokens per session scan A a24f666cecac
a11y-keyboard-playwright is a skill published in the GitHub repository AmadeusITGroup/otter (58 stars, last pushed today), licensed BSD-3-Clause. It adds 34 tokens to every session and 1,345 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
config-evals
Builds and maintains configuration-based evaluations on a workflow with the eval-config tool. Use when the user asks to set up, add, view, change, or remove an evaluation, score, grade, or judge a workflow's output, or measure answer quality against a test dataset. This is the only eval form Instance AI handles — it…
output-dev-eval-testing
Create offline evaluation tests for Output SDK workflows using @outputai/evals. Use when implementing test evaluators with verify(), creating dataset YAML files, building eval workflows, or running workflow tests via CLI.
output-eval-validate-judge
Validate LLM judges against human labels using TPR/TNR metrics and train/dev/test splits. Use after writing a judge prompt to verify it agrees with human judgment.
creating-online-evaluations
Author continuously-running online evaluations in PostHog AI observability, grounded in real failure modes you've identified. Use when the user wants evaluations that automatically score new generations or whole traces going forward — "create an eval to catch X", "continuously check that responses do Y", "turn these…
build-swiftui-interface
Use when a coding agent must design, scaffold, implement, or verify an iOS or macOS SwiftUI interface with Apple-platform state, accessibility, availability, testing, and Xcode evidence.
operate-ai-stack
Develop, test, and troubleshoot this generated AI or ML workload across its framework, model and embedding providers, retrieval stores, interfaces, training, serving, and observability layers. Use when changing prompts, tools, agents, RAG, MCP, inference, fine-tuning, evaluations, or provider integration.