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 agentmods add commands/karkranikhil/sf-ai-toolkit/create-lwcgit clone --depth 1 https://github.com/karkranikhil/sf-ai-toolkitWrote 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/karkranikhil/sf-ai-toolkit/create-lwc)<a href="https://agentmods.dev/commands/karkranikhil/sf-ai-toolkit/create-lwc"><img src="https://agentmods.dev/badge/commands/karkranikhil/sf-ai-toolkit/create-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.00000 | $0.00219 |
| Opus 5 | $0.00000 | $0.00110 |
| Sonnet 5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
create-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 5d 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
/create-lwc
Create a new Lightning Web Component with loading, error, empty state, and secure Apex integration.
Required input
- Component name and purpose
- Data needed (object, fields)
- User interactions required
- Whether an Apex controller is needed
What to create
- HTML template — with loading spinner, error display, empty state, and main content
- JavaScript controller — wire or imperative Apex, error handling, loading state
- CSS — minimal, follows existing patterns
- Apex controller (if needed) — cacheable where appropriate, CRUD/FLS enforced
- Jest test — renders correctly, handles wire data and errors
Rules
- Always show loading, error, and empty states
- Use Custom Labels for user-visible strings
- Enforce CRUD/FLS in Apex controller
- No sensitive data in component attributes or events
- Follow existing component patterns in the project
Output
Provide all files. Explain the component structure and data flow.
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.
- 5d ago First seen · 31 lines · 0 tokens per session scan A 8d9175c0a39a
create-lwc is a command published in the GitHub repository karkranikhil/sf-ai-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 219 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.