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/gen-tests)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/gen-tests"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/gen-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.
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/gen-tests"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/gen-tests.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.00420 |
| Opus 5 | $0.00000 | $0.00210 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
gen-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 10d 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
/gen-tests — Generate a bulk-safe Apex test class
Wraps agents/test-class-generator/AGENT.md. Takes a target Apex class, produces a test class targeting ≥ 85% coverage using the canonical factories in templates/apex/tests/.
Step 1 — Collect inputs
Ask:
1. Path to the Apex class to test?
Example: force-app/main/default/classes/AccountService.cls
2. Target coverage percentage? (default 85)
3. Include a 200-record bulk test? (default yes)
Say no only for utility / constant classes with no DML.
Step 2 — Load the agent
Read agents/test-class-generator/AGENT.md fully, plus every template under its Mandatory Reads.
Step 3 — Execute
Follow the 5-step plan:
- Read the source and extract its public surface
- Determine scenarios (happy / bulk / runAs / negative / callout)
- Draft the test class using
TestDataFactory,TestUserFactory,MockHttpResponseGenerator,BulkTestPattern - Estimate coverage and flag gaps
- Output checklist (no SeeAllData, meaningful assertions, etc.)
Step 4 — Deliver
Output:
- Summary (public methods, scenarios, coverage estimate)
- Full test class as a fenced block at the target path (
<Source>_Test.cls+.cls-meta.xml) - Coverage gaps with reasons
- Dependencies the user must have deployed (
TestDataFactory, etc.) - Citations
Step 5 — Recommend follow-ups
/refactor-apexif the source class is hard to test (suggests shape problems)./scan-securityon the source class if the generator noted CRUD/FLS concerns.
What this command does NOT do
- Does not execute tests.
- Does not modify the source class.
- Does not write
SeeAllData=true.
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.
- 10d ago First seen · 63 lines · 0 tokens per session scan A 7cec57fca41e
gen-tests 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 420 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
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
lg:node
Create, modify, and manage nodes in LangGraph graphs including LLM nodes, tool nodes, human-in-the-loop, subgraphs, and conditional nodes.
test
Execute a comprehensive test run for the following target.
frappe-test
Run unit and integration tests for Frappe apps with coverage reports.
implement-fix
Minimal pipeline for test-fixing tasks.