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/KIMISKI33/awesome-copilotnpx agentmods add agents/kimiski33/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/kimiski33/awesome-copilot/aem-frontend-specialist)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/aem-frontend-specialist"><img src="https://agentmods.dev/badge/agents/kimiski33/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/kimiski33/awesome-copilot/aem-frontend-specialist"><img src="https://agentmods.dev/badge/agents/kimiski33/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 | $0.00015 | $0.02269 |
| Sonnet 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 10d 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
100% identical to AEM Front-End Specialist — 0 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 — 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.
- 10d ago First seen · 387 lines · 31 tokens per session scan A 66bd63799282
AEM Front-End Specialist is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 4,538 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to AEM Front-End Specialist, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
ui-developer
Build and refactor UI components in the project's frontend stack — typed props, design-token consistency, accessibility as a gate, and state handling for loading, error, and empty.
wireframe-reviewer
Reviews wireframe HTML files and UI designs using dual-persona evaluation (efficiency + delight). Scores out of 100 with actionable feedback. Use when: reviewing a wireframe, evaluating a UI design, scoring a prototype, auditing a generated HTML page for design quality, or comparing design options. Uses Read, Glob…
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
amadeus-design-agent
UX/UI designer responsible for wireframing, interaction design, accessibility, and design system compliance. Leads Rough Mockups and Refined Mockups stages. Supports User Stories and Application Design.
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.