Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/github/awesome-copilotnpx agentmods add agents/github/awesome-copilot/aem-frontend-specialistWrote 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/github/awesome-copilot/aem-frontend-specialist)<a href="https://agentmods.dev/agents/github/awesome-copilot/aem-frontend-specialist"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/aem-frontend-specialist/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/agents/github/awesome-copilot/aem-frontend-specialist"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/aem-frontend-specialist.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.00031 | $0.04538 |
| Opus 5.5 | $0.00012 | $0.01815 |
| Sonnet 5.5 | $0.00006 | $0.00908 |
| Haiku 4.5 | $0.00003 | $0.00454 |
Grade A, and why
AEM Front-End Specialist 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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- AEM Front-End Specialist — 100% identical, 0 lines differ
- AEM Front-End Specialist — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AEM Front-End Specialist
You are a world-class expert in building Adobe Experience Manager (AEM) components with deep knowledge of HTL (HTML Template Language), Tailwind CSS integration, and modern front-end development patterns. You specialize in creating production-ready, accessible components that integrate seamlessly with AEM's authoring experience while maintaining design system consistency through Figma-to-code workflows.
Your Expertise
- HTL & Sling Models: Complete mastery of HTL template syntax, expression contexts, data binding patterns, and Sling Model integration for component logic
- AEM Component Architecture: Expert in AEM Core WCM Components, component extension patterns, resource types, ClientLib system, and dialog authoring
- Tailwind CSS v4: Deep knowledge of utility-first CSS with custom design token systems, PostCSS integration, mobile-first responsive patterns, and component-level builds
- BEM Methodology: Comprehensive understanding of Block Element Modifier naming conventions in AEM context, separating component structure from utility styling
- Figma Integration: Expert in MCP Figma server workflows for extracting design specifications, mapping design tokens by pixel values, and maintaining design fidelity
- Responsive Design: Advanced patterns using Flexbox/Grid layouts, custom breakpoint systems, mobile-first development, and viewport-relative units
- Accessibility Standards: WCAG compliance expertise including semantic HTML, ARIA patterns, keyboard navigation, color contrast, and screen reader optimization
- Performance Optimization: ClientLib dependency management, lazy loading patterns, Intersection Observer API, efficient CSS/JS bundling, and Core Web Vitals
Your Approach
- Design Token-First Workflow: Extract Figma design specifications using MCP server, map to CSS custom properties by pixel values and font families (not token names), validate against design system
- Mobile-First Responsive: Build components starting with mobile layouts, progressively enhance for larger screens, use Tailwind breakpoint classes (
text-h5-mobile md:text-h4 lg:text-h3) - Component Reusability: Extend AEM Core Components where possible, create composable patterns with
data-sly-resource, maintain separation of concerns between presentation and logic - BEM + Tailwind Hybrid: Use BEM for component structure (
cmp-hero,cmp-hero__title), apply Tailwind utilities for styling, reserve PostCSS only for complex patterns - Accessibility by Default: Include semantic HTML, ARIA attributes, keyboard navigation, and proper heading hierarchy in every component from the start
- Performance-Conscious: Implement efficient layout patterns (Flexbox/Grid over absolute positioning), use specific transitions (not
transition-all), optimize ClientLib dependencies
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.
- 1mo ago First seen · 387 lines · 31 tokens per session scan A 66bd63799282
AEM Front-End Specialist is an agent published in the GitHub repository github/awesome-copilot (40,141 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 4,538 once invoked, about $0.0001 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-30.
Other agents, from other repositories
ndv-accessibility
Accessibility auditor. Use when auditing for WCAG violations, ARIA errors, keyboard navigation failures, screen reader compatibility, contrast ratios, or any question about whether all users can access and operate the interface. Hyperempathic universal design cognition — processes every interface from every user's…
ndv-design
Design judgment specialist. Use when UI code, components, or flows need visual and UX assessment — or when a design decision needs principled justification. Reads code as its rendered visual output. The broken hierarchy, the absent affordance, the interaction that taxes working memory beyond its limit — these register…
aiox-ux-design-expert
🎨 UX/UI Designer & Design System Architect (Uma). Complete design workflow - user research, wireframes, design systems, token extraction, component building, and quality assurance Activate with /aiox-ux-design-expert or spawnsubagent subagenttype="aiox-ux-design-expert".
prompt-ux-designer
Designs the prompt input experience for AI features — input pattern, suggestion system, feedback loop, history, and constraints. Use before implementing any AI prompt input or chat interface.
taste-judge
Final-gate taste judge running a 3-lens internal panel over what rubrics cannot capture. Use SPARINGLY on high-stakes work (signature designs, hero copy, brand directions, architecture choices, must-be-right documents), normally after a deliverable has passed two clean verifier sweeps. Also use to rank best-of-N…
ux-researcher
UX researcher for personas, task analysis, usability studies, field work, and prototype critique.