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.5 | $0.00000 | $0.00161 |
| Sonnet 5.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 2mo 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.
- 2mo ago First seen · 58 lines · 0 tokens per session scan A 54477dd8145e
audit-lwc is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (4 stars, last pushed 6mo 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.
audit-lwc compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| audit-lwcBanibrataChatterjee/AwesomeSalesforceSkills | Command | 4 | 6mo ago | Apache-2.0 | A | 0 | Claude Code |
| diff-reviewcoco-research/coco | Command | 628 | today | Apache-2.0 | A | 11 | Claude Code |
| review-branchdamusix/atomic-claude | Command | 116 | 5d ago | MIT | A | 35 | Claude Code |
| refactorRchGrav/claudebox | Command | 1.2k | 1mo ago | MIT | A | 9 | Claude Code |
| spec-trace-requirementsrjmurillo/ai-agents | Command | 49 | yesterday | MIT | A | 0 | GitHub Copilot |
| merge-conflict-analysisrjmurillo/ai-agents | Command | 49 | yesterday | MIT | A | 0 | GitHub Copilot |
| initazrtydxb/procoder | Command | 211 | today | Apache-2.0 | A | 16 | Claude Code |