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/ricneves-ai/flowgrammers-skillsWrote 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/commands/ricneves-ai/flowgrammers-skills/a11y-audit)<a href="https://agentmods.dev/commands/ricneves-ai/flowgrammers-skills/a11y-audit"><img src="https://agentmods.dev/badge/commands/ricneves-ai/flowgrammers-skills/a11y-audit/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/commands/ricneves-ai/flowgrammers-skills/a11y-audit"><img src="https://agentmods.dev/badge/commands/ricneves-ai/flowgrammers-skills/a11y-audit.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.00043 | $0.00738 |
| Opus 5 | $0.00022 | $0.00369 |
| Sonnet 5 | $0.00009 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
a11y-audit 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/a11y-audit
Varre um projeto frontend em busca de problemas de acessibilidade WCAG 2.2, exibe correções e verifica contraste de cores.
Uso
/a11y-audit # Varre o projeto atual
/a11y-audit ./src # Varre um diretório específico
/a11y-audit ./src --fix # Varre e aplica correções automáticas
O que faz
Etapa 1: Varredura
Executa o scanner de acessibilidade no diretório alvo:
python3 {skill_path}/scripts/a11y_scanner.py {path} --json
Agrupa os achados por severidade (crítico → sério → moderado → leve).
Exibe um resumo:
Auditoria A11y: ./src
Crítico: 3 | Sério: 7 | Moderado: 12 | Leve: 5
Arquivos varridos: 42 | Arquivos com problemas: 15
Etapa 2: Correção
Para cada achado (começando pelos críticos):
- Lê o arquivo afetado
- Exibe a violação com contexto (antes)
- Aplica a correção de
references/framework-a11y-patterns.md - Exibe o resultado (depois)
Correções automáticas (aplicadas sem perguntar):
alt=""ausente em imagens decorativas- Atributo
langausente no<html> - Valores de
tabindex> 0 → definidos como 0 type="button"ausente em botões não-submit- Remoção de outline sem substituto → adiciona estilos
:focus-visible
Problemas que exigem decisão do usuário (exibe a correção e pergunta):
- Texto alternativo ausente (requer descrição do usuário)
- Labels de formulário ausentes (requer texto do label)
- Reestruturação de headings (pode afetar layout)
- Alterações de papel ARIA (pode afetar funcionalidade)
Etapa 3: Verificação de Contraste
Se houver arquivos CSS, executa o verificador de contraste:
python3 {skill_path}/scripts/contrast_checker.py --batch {path}
Para cada par de cores com falha, sugere alternativas acessíveis.
Etapa 4: Relatório
Gera um relatório markdown em a11y-report.md:
- Resumo executivo (aprovado/reprovado, contagem de problemas)
- Achados por arquivo com diffs antes/depois
- Itens pendentes de revisão manual
- Cobertura de critérios WCAG
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 · 85 lines · 0 tokens per session scan A 9a5eb1a0f627
a11y-audit is a command published in the GitHub repository ricneves-ai/flowgrammers-skills (112 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 738 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-09-03.
Other commands, from other repositories
color-specialist
Use when colour is failing. Contrast below AA, a palette with no system behind it, dark mode that is only inverted light mode, or semantic colours that carry no meaning.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2 and the axe-core reference.
revisar-ui
Auditoria visual retroativa de 6 pilares do código frontend implementado.
colorize
Introduce or rework color strategy.
polish
Final pre-ship pass — apply all three lenses to fix the target.