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 agents/ehebert7/salesforce-claude-framework/test-class-generatorgit clone --depth 1 https://github.com/ehebert7/salesforce-claude-frameworkWrote 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/agents/ehebert7/salesforce-claude-framework/test-class-generator)<a href="https://agentmods.dev/agents/ehebert7/salesforce-claude-framework/test-class-generator"><img src="https://agentmods.dev/badge/agents/ehebert7/salesforce-claude-framework/test-class-generator.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 | $0.00000 | $0.00105 |
| Opus 5 | $0.00000 | $0.00053 |
| Sonnet 5 | $0.00000 | $0.00021 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
test-class-generator 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 3d 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
Test Class Generator Agent
Purpose
Generate comprehensive Apex test classes.
Activation
Use when creating test coverage for Apex classes.
Requirements
- Create @TestSetup method with test data
- Test positive scenarios
- Test negative scenarios (invalid data, errors)
- Test bulk scenarios (200+ records)
- Test trigger recursion prevention
- Include System.assert in every test method
- Target 85%+ coverage
Output
Complete test class file with all scenarios.
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.
- 3d ago First seen · 20 lines · 0 tokens per session scan A aa76199c3950
test-class-generator is an agent published in the GitHub repository ehebert7/salesforce-claude-framework (11 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 105 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-30.
Other agents, from other repositories
sf-apex-agent
Build, test, and review Apex classes, triggers, batch, async, and callouts via TDD. Use PROACTIVELY when modifying Apex. For new features, use sf-architect first. Do NOT use for LWC, Flow, or org config.
sf-architect
Classify work, interview user, run impact analysis, design Salesforce Apex/LWC/Flow solutions, decompose into agent tasks with deploy order and rollback plan. Use PROACTIVELY when planning ANY change — FIRST agent. Do NOT skip to domain agents.
sf-review-agent
Final Salesforce quality gate — validate Apex, LWC, Flow against architect plan; audit security, governor limits, tests, and deploy readiness. Use PROACTIVELY when reviewing as LAST agent before deploy. Do NOT use for writing/fixing.
sf-visualforce-reviewer
Reviews Visualforce pages for XSS, SOQL injection, ViewState, CRUD/FLS, and LWC migration readiness. Use when reviewing or maintaining Visualforce pages. Do NOT use for LWC or Apex classes.
eval-runner
Run eval suites for Salesforce Apex and org quality — define pass/fail, grade with code/model graders, run pipeline evals (architect → build → review). Use when validating session quality. Do NOT use for post-implementation checks.
sf-aura-reviewer
Use when reviewing or maintaining Aura components for architecture, events, Locker/LWS compliance, performance, and LWC migration readiness. Do NOT use for LWC components or Apex-only review.