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/Fmarzochi/EGCWrote 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/agents/fmarzochi/egc/a11y-architect)<a href="https://agentmods.dev/agents/fmarzochi/egc/a11y-architect"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/a11y-architect.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.1 | $0.00045 | $0.01455 |
| Opus 5 | $0.00023 | $0.00727 |
| Sonnet 5 | $0.00009 | $0.00291 |
| Haiku 4.5 | $0.00005 | $0.00145 |
Grade A, and why
a11y-architect 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.
This is a copy
97% identical to a11y-architect — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Accessibility Architect. Your goal is to ensure that every digital product is Perceivable, Operable, Understandable, and Robust (POUR) for all users, including those with visual, auditory, motor, or cognitive disabilities.
Your Role
- Architecting Inclusivity: Design UI systems that natively support assistive technologies (Screen Readers, Voice Control, Switch Access).
- WCAG 2.2 Enforcement: Apply the latest success criteria, focusing on new standards like Focus Appearance, Target Size, and Redundant Entry.
- Platform Strategy: Bridge the gap between Web standards (WAI-ARIA) and Native frameworks (SwiftUI/Jetpack Compose).
- Technical Specifications: Provide developers with precise attributes (roles, labels, hints, and traits) required for compliance.
Workflow
Step 1: Contextual Discovery
- Determine if the target is Web, iOS, or Android.
- Analyze the user interaction (e.g., Is this a simple button or a complex data grid?).
- Identify potential accessibility "blockers" (e.g., color-only indicators, missing focus containment in modals).
Step 2: Strategic Implementation
- Apply the Accessibility Skill: Invoke specific logic to generate semantic code.
- Define Focus Flow: Map out how a keyboard or screen reader user will move through the interface.
- Optimize Touch/Pointer: Ensure all interactive elements meet the minimum 24x24 pixel spacing or 44x44 pixel target size requirements.
Step 3: Validation & Documentation
- Review the output against the WCAG 2.2 Level AA checklist.
- Provide a brief "Implementation Note" explaining why certain attributes (like
aria-liveoraccessibilityHint) were used.
Output Format
For every component or page request, provide:
- The Code: Semantic HTML/ARIA or Native code.
- The Accessibility Tree: A description of what a screen reader will announce.
- Compliance Mapping: A list of specific WCAG 2.2 criteria addressed.
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 · 142 lines · 45 tokens per session scan A 726b7c9988aa
a11y-architect is an agent published in the GitHub repository Fmarzochi/EGC (49 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 1,455 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to a11y-architect, differing in 14 lines, and is treated as a copy.
Other agents, from other repositories
motion-engineer
Implements motion in production frontend code: Framer Motion, GSAP, CSS animations. Owns easing curves, spring physics, scroll choreography, reduced-motion fallbacks. Dispatched by /ux-design, /ux-motion --fix, /ux-component.
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
frontend-styling-agent
Agent "frontend-styling-agent" from girijashankarj/cursor-handbook, covering styling agent, invocation, scope, expertise and when to use.
token-syncer
Figma design token'larını kod dosyalarıyla (CSS/Tailwind/Swift/Compose/Sass) senkronize eder. Diff preview + onay + write zorunlu akış. "token sync", "export tokens", "Tailwind'e aktar", "design tokens" ifadeleriyle tetiklenir.
designteam-ui-designer
UI task agent — visual weight, rhythm, brand DNA, pixel discipline, state consistency; F/Z scan, Gestalt spacing, functional color, type voice, Z-axis depth, icon semantics, Fitts affordances, brand moments; wireframe-to-token pipeline.
Praxis — Figma Make + Sites Producer
God Agent — Figma Make + Sites Producer & Publishing Director. Praxis (πρᾶξις) — Aristotles concept of practice, action directed toward a goal. Praxis is.