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/BanibrataChatterjee/AwesomeSalesforceSkillsWrote 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/commands/banibratachatterjee/awesomesalesforceskills/audit-lwc)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/audit-lwc"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/audit-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/commands/banibratachatterjee/awesomesalesforceskills/audit-lwc"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/audit-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.00000 | $0.00402 |
| Opus 5 | $0.00000 | $0.00201 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
audit-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 11d 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.
What it actually says
/audit-lwc — Accessibility + performance + security audit of an LWC bundle
Wraps agents/lwc-auditor/AGENT.md. Scans one Lightning Web Component bundle and returns ranked findings with paste-ready fixes.
Step 1 — Collect inputs
Ask:
1. Path to the LWC bundle directory?
Example: force-app/main/default/lwc/accountDetail
Step 2 — Load the agent
Read agents/lwc-auditor/AGENT.md fully + the LWC skills and the templates/lwc/ skeleton and patterns.
Step 3 — Execute
Follow the 6-step plan:
- Parse the bundle (
.html,.js,.css,.js-meta.xml, tests) - Accessibility checks (missing alt, div-as-button, icon-only buttons, label-less inputs, heading hierarchy, keyboard traps, live regions)
- Performance checks (imperative-in-render, missing keys, wire without params, synchronous heavy loops)
- Security checks (innerHTML, eval, hardcoded API names, FLS on @AuraEnabled returns)
- Testing gaps (missing tests, missing wire emits, missing jest.config)
- Recommendations mapped to skeleton / patterns
Step 4 — Deliver
- Bundle summary: public API, wires, imperative calls, test coverage %
- Findings table by severity
- Per-finding before/after code block for P0 and P1
- Skeleton alignment notes
- Citations
Step 5 — Recommend follow-ups
/gen-testsfor the Apex backing any wires/imperative calls/scan-securityon any @AuraEnabled Apex the bundle depends on
What this command does NOT do
- Does not modify files.
- Does not run Jest.
- Does not evaluate visual design beyond accessibility-relevant checks.
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.
- 11d ago First seen · 58 lines · 0 tokens per session scan A 54477dd8145e
audit-lwc is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 402 tokens. 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 commands, from other repositories
devkit.react.code-review
Provides comprehensive React 19 + Tailwind CSS code review focusing on modern patterns, hooks, Server Components, Actions, performance, accessibility, and Tailwind best practices. Use when reviewing React code changes or before merging pull requests.
critique
Design lens critique covering visual hierarchy, clarity, and anti-slop patterns — produces a findings table, no code edits unless asked. Use when the user wants a design review, says "what's wrong with this UI", or needs a second opinion before a handoff or presentation.
check-architecture
Angular Architecture Review.
react-patterns
Review React code for performance and composition patterns — 50+ rules ranked by impact.
fec-review
Conduct a standardized review of the specified file or recently changed front-end code, output a graded review report and save it as a Markdown file.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.