A command that creates or updates tests for Salesforce Apex code and Lightning Web Components. Apex is Salesforce’s programming language, while LWC is its web-component framework.

Use it for Apex classes or triggers and for LWC components. It produces test files covering positive and negative cases, large batches, permissions, user interactions, server calls, and errors.

It helps cover normal, error, bulk, security, rendering, and interaction cases that are easy to miss when writing tests manually.

write-tests — Command for Claude Code by karkranikhil/sf-ai-toolkit

Install

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.

Clone the repo

git clone --depth 1 https://github.com/karkranikhil/sf-ai-toolkit

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/karkranikhil/sf-ai-toolkit/write-tests/github.svg)](https://agentmods.dev/commands/karkranikhil/sf-ai-toolkit/write-tests)

Your own site

<a href="https://agentmods.dev/commands/karkranikhil/sf-ai-toolkit/write-tests"><img src="https://agentmods.dev/badge/commands/karkranikhil/sf-ai-toolkit/write-tests/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/karkranikhil/sf-ai-toolkit/write-tests"><img src="https://agentmods.dev/badge/commands/karkranikhil/sf-ai-toolkit/write-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 222 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00222
Opus 5.5	$0.00000	$0.00089
Sonnet 5.5	$0.00000	$0.00044
Haiku 4.5	$0.00000	$0.00022

Measured 2mo ago against content hash 83f3bc566969, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-tests 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.

examples/existing-project-after/.claude/commands/write-tests.md · 29 lines

What it actually says

/write-tests

Create or update Apex tests and LWC tests for the specified code.

For Apex tests

Read the existing class or trigger being tested.
Identify the main scenarios: positive, negative, bulk (200+ records), security.
Create or update the test class using this structure:
- @TestSetup for shared test data
- Individual test methods for each scenario
- Test.startTest() / Test.stopTest() around DML
Do not use SeeAllData=true.
Cover at least: positive case, null/empty inputs, bulk (200 records), with/without sharing.

For LWC Jest tests

Read the component JS file.
Create a Jest test file that:
- Tests initial render
- Tests user interactions
- Mocks wire adapters and Apex calls
- Tests error states
Follow the patterns in the existing __tests__ folders.

Output

Provide the complete test file(s). State the expected coverage improvement.

Changes

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 · 29 lines · 0 tokens per session scan A 83f3bc566969

Subscribe to this mod's changes

write-tests is a command published in the GitHub repository karkranikhil/sf-ai-toolkit (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 222 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.

Testing Unit testing

write-tests next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
write-testskarkranikhil/sf-ai-toolkit	Command	2	6mo ago	MIT	A	0	Claude Code
test-tddguanyang/open-agent-hub	Command	986	today	MIT	A	32	Claude Code
kill-mutantsswingerman/engineer	Command	162	10d ago	MIT	A	29	Claude Code
lg:nodeTheLobbi/claude	Command	21	7d ago	MIT	A	34	Claude Code
test-auditacaprino/daodan	Command	9	5d ago	MIT	A	88	Claude Code
story-and-testepam/ai-dial-ui-kit	Command	10	yesterday	Apache-2.0	A	0	Claude Code, Cursor
testOmar-Obando/qwen-orchestrator	Command	53	4mo ago	MIT	A	0	Claude Code