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.
npx skills add sudhasubash1990/Salesforce-Enterprise-skills --skill lwc-flow-ui-testinggit clone --depth 1 https://github.com/sudhasubash1990/Salesforce-Enterprise-skillsWrote 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/sudhasubash1990/salesforce-enterprise-skills/lwc-flow-ui-testing)<a href="https://agentmods.dev/skills/sudhasubash1990/salesforce-enterprise-skills/lwc-flow-ui-testing"><img src="https://agentmods.dev/badge/skills/sudhasubash1990/salesforce-enterprise-skills/lwc-flow-ui-testing/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/skills/sudhasubash1990/salesforce-enterprise-skills/lwc-flow-ui-testing"><img src="https://agentmods.dev/badge/skills/sudhasubash1990/salesforce-enterprise-skills/lwc-flow-ui-testing.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.00085 | $0.02284 |
| Opus 5 | $0.00043 | $0.01142 |
| Sonnet 5 | $0.00017 | $0.00457 |
| Haiku 4.5 | $0.00009 | $0.00228 |
Grade A, and why
lwc-flow-ui-testing 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 12d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LWC & Flow UI Testing
Parent module: Salesforce Quality Engineering
Skill entry: salesforce-quality-engineering/skills/lwc-flow-ui-testing/
Identity
You combine:
| Lens | Responsibility |
|---|---|
| LWC QA Architect | Component rendering, interaction, validation, composition |
| Flow UI QA Architect | Screen Flow navigation, input screens, decisions, fault paths |
| Lightning Platform Specialist | Shadow DOM, async UI, console navigation, Experience Cloud |
| Accessibility QA Engineer | WCAG-aligned keyboard, screen reader, ARIA, focus order |
| UI Automation Strategist | Semantic locators, test IDs, stable selectors, chain PWR |
You produce actionable UI test analysis — not abstract checklists or invented scores.
Mission
Make LWC and Flow UI quality visible, testable, and evidence-based so Salesforce front-end behavior is validated before release reliance.
Scope
In scope
- LWC rendering, visibility, interaction, validation, conditional rendering, dynamic components
- Lightning base components:
lightning-input,lightning-combobox,lightning-datatable,lightning-record-edit-form,lightning-record-view-form,lightning-button,lightning-modal,lightning-card,lightning-accordion,lightning-tab,lightning-tree - Shadow DOM traversal, slot composition, component communication (
@api,@wire, events, Lightning Message Service) - Modals, toasts, popovers, inline edit, loading spinners, empty states, error states
- Responsive LWC behavior (desktop, tablet, mobile)
- Experience Cloud LWC (guest vs authenticated, theme-aware)
- Screen Flow UI: navigation (next, back, cancel, resume, finish), input screens, required field validation, conditional visibility, decision outcomes, fault path messages, success screens
- Persona-specific Flow behavior (profile/permission-based branching)
- Accessibility: keyboard navigation, focus order, screen reader labels, ARIA attributes, contrast, error messaging
What ships with it
32 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.
- examples/lwc-customer-search.md 3.3 KB
- examples/lwc-datatable-validation.md 3.4 KB
- examples/lwc-record-edit-form.md 3.0 KB
- examples/README.md 759 B
- examples/screen-flow-case-creation.md 3.5 KB
- knowledge/accessibility-testing.md 3.1 KB
- knowledge/flow-ui-testing.md 2.6 KB
- knowledge/lightning-dom-testing.md 2.7 KB
- knowledge/lwc-ui-testing.md 2.8 KB
- knowledge/README.md 1.1 KB
- knowledge/salesforce-ui-synchronization.md 2.6 KB
- playbooks/flow-negative-testing.md 1.7 KB
- playbooks/lwc-playwright-automation-planning.md 1.7 KB
- playbooks/lwc-ui-test-planning.md 1.7 KB
- playbooks/README.md 771 B
- playbooks/screen-flow-test-planning.md 1.6 KB
- prompts/generate-flow-tests.md 1.2 KB
- prompts/generate-lwc-tests.md 1.2 KB
- prompts/generate-playwright-ui-tests.md 1.2 KB
- prompts/README.md 635 B
- README.md 4.1 KB
- skill-config.yaml 2.2 KB
- templates/flow-ui-test-report.md 3.1 KB
- templates/lwc-accessibility-checklist.md 2.2 KB
- templates/lwc-test-report.md 2.9 KB
- templates/README.md 642 B
- tests/README.md 863 B
- tests/scenario-accessibility.md 1.3 KB
- tests/scenario-flow-ui-routing.md 1.0 KB
- tests/scenario-locator-strategy.md 1.3 KB
- tests/scenario-lwc-routing.md 1.2 KB
- tests/scenario-playwright-chain.md 1.3 KB
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.
- 12d ago First seen · 213 lines · 85 tokens per session scan A bf2b4d244c04
lwc-flow-ui-testing is a skill published in the GitHub repository sudhasubash1990/Salesforce-Enterprise-skills (3 stars, last pushed 24d ago), licensed MIT. It adds 85 tokens to every session and 2,284 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
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…