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/KIMISKI33/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/kimiski33/awesome-copilot/salesforce-aura-lwc)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/salesforce-aura-lwc"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/salesforce-aura-lwc/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/salesforce-aura-lwc"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/salesforce-aura-lwc.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.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 7d 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 Salesforce UI Development (Aura & LWC) — 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 — 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.
- 7d 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 KIMISKI33/awesome-copilot (1 stars, last pushed 4d ago), 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. It is 100% identical to Salesforce UI Development (Aura & LWC), differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
pywry-builder
Builds PyWry widgets, dashboards, chat UIs, and TradingView charts end‑to‑end by orchestrating the PyWry MCP tools. Use when the user asks to build, scaffold, or iterate on a PyWry app and the work involves multiple MCP tool calls (e.g. create widget → populate data → add toolbar → wire events → export).
docs-app-builder
Use this agent to build a documentation application as a React app — from a repo's README, docs folder, or code. Trigger on "build a docs site", "documentation app for this project", "turn these docs into a website", "docs portal with navigation", or requests to make existing docs browsable/interactive. Returns a…