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/easingthemes/dx-aem-flownpx agentmods add skills/easingthemes/dx-aem-flow/aem-fe-verifyWrote 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/easingthemes/dx-aem-flow/aem-fe-verify)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/aem-fe-verify"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/aem-fe-verify.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 103 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00085 | $0.04292 |
| Opus 5 | $0.00043 | $0.02146 |
| Sonnet 5 | $0.00017 | $0.00858 |
| Haiku 4.5 | $0.00009 | $0.00429 |
Grade A, and why
aem-fe-verify 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 8d 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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform note: This skill uses context: fork + agent: aem-fe-verifier for isolated execution. If subagent dispatch is unavailable (e.g., VS Code Chat), you may run inline but AEM MCP tools (AEM/*, playwright/*) must be available. If they are not, inform the user: "Frontend verification requires AEM and Playwright MCP servers. Please use Claude Code or Copilot CLI."
You visually verify a component's rendered output on a local AEM instance against the Figma design or requirements. You create/reuse a demo page, screenshot the component in wcmmode=disabled, compare using multimodal vision, and fix code gaps — up to 3 iterations.
Use ultrathink for visual comparison — identifying layout, spacing, and color differences between two screenshots requires careful analysis.
Pipeline Position
| Field | Value |
|---|---|
| Called by | /dx-agent-all (Phase 4, after build), manual invocation |
| Follows | /dx-step-build (code deployed to local AEM) |
| Precedes | /dx-step-verify or /dx-pr-commit |
| Output | Verification report + screenshots in spec directory |
| Idempotent | No — re-runs produce fresh verification |
Flow
digraph aem_fe_verify {
"Hard gate: localhost check" [shape=box];
"Gate passed?" [shape=diamond];
"STOP: blocked" [shape=doublecircle];
"Resolve component and spec directory" [shape=box];
"Ensure demo page exists" [shape=box];
"Determine reference for comparison" [shape=box];
"MCP fallback check" [shape=box];
"Playwright available?" [shape=diamond];
"AEM MCP available?" [shape=diamond];
"Content-only verification (AEM MCP)" [shape=box];
"Code-only verification (fallback)" [shape=box];
"Screenshot component on local AEM" [shape=box];
"Visual comparison" [shape=box];
"Gaps found?" [shape=diamond];
"Iteration < 3?" [shape=diamond];
"Fix code + rebuild + redeploy" [shape=box];
"Re-screenshot and re-compare" [shape=box];
"All gaps fixed or only minor?" [shape=diamond];
"Write verification report" [shape=box];
"Present summary" [shape=doublecircle];
"Hard gate: localhost check" -> "Gate passed?";
"Gate passed?" -> "STOP: blocked" [label="no"];
"Gate passed?" -> "Resolve component and spec directory" [label="yes"];
"Resolve component and spec directory" -> "Ensure demo page exists";
"Ensure demo page exists" -> "Determine reference for comparison";
"Determine reference for comparison" -> "MCP fallback check";
"MCP fallback check" -> "Playwright available?";
"Playwright available?" -> "Screenshot component on local AEM" [label="yes"];
"Playwright available?" -> "AEM MCP available?" [label="no"];
"AEM MCP available?" -> "Content-only verification (AEM MCP)" [label="yes"];
"AEM MCP available?" -> "Code-only verification (fallback)" [label="no"];
"Content-only verification (AEM MCP)" -> "Write verification report";
"Code-only verification (fallback)" -> "Write verification report";
"Screenshot component on local AEM" -> "Visual comparison";
"Visual comparison" -> "Gaps found?";
"Gaps found?" -> "Write verification report" [label="no"];
"Gaps found?" -> "Iteration < 3?" [label="yes"];
"Iteration < 3?" -> "Fix code + rebuild + redeploy" [label="yes"];
"Iteration < 3?" -> "Write verification report" [label="no, max reached"];
"Fix code + rebuild + redeploy" -> "Re-screenshot and re-compare";
"Re-screenshot and re-compare" -> "All gaps fixed or only minor?";
"All gaps fixed or only minor?" -> "Write verification report" [label="yes"];
"All gaps fixed or only minor?" -> "Iteration < 3?" [label="no, major remain"];
"Write verification report" -> "Present summary";
}
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 368 lines · 85 tokens per session scan A e0cd1b052f6a
aem-fe-verify is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 7d ago), licensed MIT. It adds 85 tokens to every session and 4,292 once invoked, about $0.0004 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
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…