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 agentmods add skills/trebormc/drupal-ai-agents/drupal-accessibilitynpx skills add trebormc/drupal-ai-agents --skill drupal-accessibilitygit clone --depth 1 https://github.com/trebormc/drupal-ai-agentsWrote 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/trebormc/drupal-ai-agents/drupal-accessibility)<a href="https://agentmods.dev/skills/trebormc/drupal-ai-agents/drupal-accessibility"><img src="https://agentmods.dev/badge/skills/trebormc/drupal-ai-agents/drupal-accessibility.svg" alt="Measured on agentmods" 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 | $0.00182 | $0.01355 |
| Opus 5 | $0.00091 | $0.00678 |
| Sonnet 5 | $0.00036 | $0.00271 |
| Haiku 4.5 | $0.00018 | $0.00136 |
Grade A, and why
drupal-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 4d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drupal Accessibility
Baseline: WCAG 2.2 AA. New in 2.2 and most often missed by generated UI: SC 2.5.8 Target Size — every pointer/touch target at least 24×24 CSS pixels (44px remains the comfortable standard for primary touch targets).
Core principle: Drupal idioms over hand-rolled ARIA
Drupal's APIs already emit correct, tested accessibility output. Hand-written ARIA on top of them is at best redundant and at worst conflicts with what core generates:
| Instead of hand-writing | Use |
|---|---|
aria-describedby/aria-labelledby on form fields |
Form API #title, #description — associations are generated |
role="navigation" on <nav>, role="button" on <button>, role="list" on <ul> |
Nothing — native semantics already provide it |
Custom aria-live region |
`Drupal.announce('Message', 'polite' |
| Manual Tab-key trapping in modals | Drupal.tabbingManager (Drupal.tabbingManager.constrain(...)) |
Ad-hoc .sr-only / custom hiding CSS |
Core utilities: see hiding table below |
Raw HTML strings in #markup |
Render API #type elements (semantic markup for free) |
Semantic HTML5 first; ARIA only fills genuine gaps.
#states is NOT #access
#states shows/hides via CSS (display: none) — the element stays in the DOM and in
form processing. #access => FALSE removes it entirely.
- User-driven progressive disclosure (show field B when checkbox A is on) →
#states. - Permission-based or unconditional hiding →
#access. Using#stateshere leaves the "hidden" field submittable and processable — an accessibility AND security defect.
Hiding content correctly
| Utility | Effect | Use for |
|---|---|---|
.visually-hidden |
Hidden visually, read by screen readers | Labels/headings that give SR users context |
.visually-hidden.focusable |
Appears on keyboard focus | Skip links |
.hidden / [hidden] |
Hidden from everyone | Content genuinely not available yet |
#access => FALSE |
Not rendered at all | Permission-based removal |
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.
- 4d ago First seen · 110 lines · 182 tokens per session scan A c97e7582498b
drupal-accessibility is a skill published in the GitHub repository trebormc/drupal-ai-agents (10 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 182 tokens to every session and 1,355 once invoked, about $0.0009 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…