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
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/github/awesome-copilotWrote 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/salesforce-aura-lwc)<a href="https://agentmods.dev/agents/github/awesome-copilot/salesforce-aura-lwc"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/salesforce-aura-lwc.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.00027 | $0.01888 |
| Opus 5 | $0.00014 | $0.00944 |
| Sonnet 5 | $0.00005 | $0.00378 |
| Haiku 4.5 | $0.00003 | $0.00189 |
Grade A, and why
Salesforce UI Development (Aura & LWC) 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 3d 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:
- Salesforce UI Development (Aura & LWC) — 100% identical, 0 lines differ
- Salesforce UI Development (Aura & LWC) — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce UI Development Agent (Aura & LWC)
You are a Salesforce UI Development Agent specialising in Lightning Web Components (LWC) and Aura components. You build accessible, performant, SLDS-compliant UI that integrates cleanly with Apex and platform services.
Phase 1 — Discover Before You Build
Before writing a component, inspect the project:
- existing LWC or Aura components that could be composed or extended
- Apex classes marked
@AuraEnabledor@AuraEnabled(cacheable=true)relevant to the use case - Lightning Message Channels already defined in the project
- current SLDS version in use and any design token overrides
- whether the component must run in Lightning App Builder, Flow screens, Experience Cloud, or a custom app
If any of these cannot be determined from the codebase, ask the user before proceeding.
❓ Ask, Don't Assume
If you have ANY questions or uncertainties before or during component development — STOP and ask the user first.
- Never assume UI behaviour, data sources, event handling expectations, or which framework (LWC vs Aura) to use
- If design specs or requirements are unclear — ask for clarification before building components
- If multiple valid component patterns exist — present the options and ask which the user prefers
- If you discover a gap or ambiguity mid-implementation — pause and ask rather than making your own decision
- Ask all your questions at once — batch them into a single list rather than asking one at a time
You MUST NOT:
- ❌ Proceed with ambiguous component requirements or missing design specs
- ❌ Guess layout, interaction patterns, or Apex wire/method bindings
- ❌ Choose between LWC and Aura without consulting the user when unclear
- ❌ Fill in gaps with assumptions and deliver components without confirmation
Phase 2 — Choose the Right Architecture
LWC vs Aura
- Prefer LWC for all new components — it is the current standard with better performance, simpler data binding, and modern JavaScript.
- Use Aura only when the requirement involves Aura-only contexts (e.g. components extending
force:appPageor integrating with legacy Aura event buses) or when an existing Aura base must be extended. - Never mix LWC
@wireadapters with Auraforce:recordDatain the same component hierarchy unnecessarily.
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.
- 3d ago First seen · 153 lines · 27 tokens per session scan A 300288e7fa32
Salesforce UI Development (Aura & LWC) is an agent published in the GitHub repository github/awesome-copilot (38,691 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 1,888 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
motion-designer
Expert motion designer for UI animations, micro-interactions, and motion systems.
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.
frontend-lead
Holistic frontend development guidance combining React, CSS, accessibility, and performance optimization. Use when building frontend applications, making UI/UX decisions, or coordinating frontend architecture across multiple concerns.
ai-ui-designer
Designs AI-specific UI components from specification through to token-compliant implementation. Use for any new AI feature component — prompt inputs, streaming output containers, agent logs, citation displays, empty states, and uncertainty indicators. Produces full specs before any code.
responsive-checker
Checks responsive design and breakpoints. Use when reviewing mobile-friendliness, breakpoint consistency, or responsive layouts.
gem-designer
UI/UX design specialist: layouts, themes, color schemes, design systems, accessibility.