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 joaoguirunas/team-os --skill accessibilitygit clone --depth 1 https://github.com/joaoguirunas/team-osWrote 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/joaoguirunas/team-os/accessibility)<a href="https://agentmods.dev/skills/joaoguirunas/team-os/accessibility"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/accessibility/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/joaoguirunas/team-os/accessibility"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/accessibility.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.00082 | $0.03027 |
| Opus 5.5 | $0.00033 | $0.01211 |
| Sonnet 5.5 | $0.00016 | $0.00605 |
| Haiku 4.5 | $0.00008 | $0.00303 |
Grade A, and why
accessibility 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 2d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acessibilidade (a11y)
Auditar e corrigir acessibilidade com base na WCAG 2.2 e nas auditorias de acessibilidade do Lighthouse. Objetivo: conteúdo utilizável por todo mundo, inclusive pessoas com deficiência. Alvo padrão: nível AA.
Quando usar esta vs. web-design-guidelines: esta audita e corrige acessibilidade contra a WCAG (com evidência de ferramenta e teste manual). Para revisar código de UI contra as guidelines gerais de interface da Vercel (formulários, tipografia, performance, i18n), use web-design-guidelines.
Carregue quando precisar (não leia tudo de saída):
references/A11Y-PATTERNS.md— exemplos de código por critério (alt, contraste, teclado, foco, alvo, formulários, erros, ARIA, live regions, modal, skip link, arrastar, atalhos de leitor de tela).references/NEXTJS-TAILWIND.md— padrões e checklist da stack de sites do CT (Next.js App Router + Tailwind + shadcn/ui).references/WCAG.md— critérios por nível, padrões ARIA comuns, mudanças 2.1 → 2.2, ferramentas.
Fluxo de auditoria com evidência
Quando houver página renderizada:
- Auditoria automática ao vivo. Rode o Lighthouse (categoria Accessibility) na página. Com Chrome DevTools MCP, use
lighthouse_audit; em página pública, modo navegação mobile; em fluxo autenticado ou com estado criado pelo usuário, modo snapshot (recarregar perderia o estado). - Localize pelos nós que falharam. Use os seletores/nós reprovados na auditoria para achar o componente ou template responsável — não varra o repositório inteiro atrás de padrões genéricos.
- Inspecione a árvore de acessibilidade renderizada (nomes, papéis, estados, landmarks, hierarquia de headings) — com Chrome DevTools MCP,
take_snapshot; ou oread_pagedo navegador embutido. Percorra o fluxo afetado só com teclado. - Corrija na fonte e re-audite: rode de novo a mesma auditoria e a mesma interação manual, e registre o antes/depois.
Sem ferramentas ao vivo, use a CLI (abaixo) e faça as mesmas checagens manuais. Ferramenta automática pega só uma parte das barreiras: nota 100 não é conformidade WCAG, e nota baixa não substitui evidência por achado (componente, critério, nó, correção).
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · -358 lines · +16 tokens per session 475627993b51
- 27d ago Changed 38443e13ea72
- 1mo ago Changed · +62 lines · +15 tokens per session 93301a84a08c
- 1mo ago First seen · 441 lines · 51 tokens per session scan A 65021e9ccab7
accessibility is a skill published in the GitHub repository joaoguirunas/team-os (5 stars, last pushed 3d ago), licensed MIT. It adds 82 tokens to every session and 3,027 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
information-architecture
Design the structure of a website or product including sitemap, navigation, URL structure, content types, taxonomy, and labeling. Use this skill whenever the user asks to plan a sitemap, design navigation, structure URLs, define content types, build taxonomies, design site search, or organize content at the system…
journey-mapping
Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction across an experience, align teams on the…
brand-style-guide
Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts. Use this skill whenever the user wants to create brand guidelines, document an existing brand, build a brand book, audit an existing style…
visual-qa
Runs rigorous visual QA across web, terminal, and paginated surfaces: an Apple HIG-based checklist, paired light/dark captures at phone and desktop widths, screenshot evidence, and a per-item PASS/FAIL verdict. Use for any UI build or change, or when asked whether a page, component, or TUI looks right or follows the…
frontend
Builds, styles, and polishes anything drawn with HTML, CSS, or SVG: web UI, pages, components, HTML reports rendered to PDF or print, figures, PNG/SVG diagrams, slides, and images for Notion or Slack. Use for any styling, layout, animation, or visual-quality task, or when asked to make something look or feel a certain…
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…