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 skills add divingsbysangam/salesforce-compound-engineering-plugin --skill apex-generategit clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-pluginWrote 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/skills/divingsbysangam/salesforce-compound-engineering-plugin/apex-generate)<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/apex-generate"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/apex-generate/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/skills/divingsbysangam/salesforce-compound-engineering-plugin/apex-generate"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/apex-generate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00214 | $0.01048 |
| Opus 5 | $0.00107 | $0.00524 |
| Sonnet 5 | $0.00043 | $0.00210 |
| Haiku 4.5 | $0.00021 | $0.00105 |
Grade A, and why
apex-generate 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/apex-generate
Principles enforced: 1 (preserve the quality ceiling), 2 (verifiability), 5 (taste over typing). See
PRINCIPLES.md.
Required reads
Procedure lives in sibling files, not only in this orchestrator:
- Required inputs (gather or infer before authoring) — read
references/required-inputs-gather-or-infer-before-authoring.mdbefore acting on this section. - Step 0: Pre-implementation research (parallel, Principle 7) — read
references/step-0-pre-implementation-research-parallel-principle-7.mdbefore acting on this section. - Phase 1: Author the production class — read
references/phase-1-author-the-production-class.mdbefore acting on this section. - Phase 2: Author the test class (mandatory, Principle 2) — read
references/phase-2-author-the-test-class-mandatory-principle-2.mdbefore acting on this section. - Phase 3: Validate (mandatory before reporting, Principle 2) — read
references/phase-3-validate-mandatory-before-reporting-principle-2.mdbefore acting on this section. - Phase 4: Report — read
references/phase-4-report.mdbefore acting on this section. - Test-only mode (
apex-generate test for) — readreferences/test-only-mode-apex-generate-test-for.mdbefore acting on this section. - Hand off to /sf-compound — read
references/hand-off-to-sf-compound.mdbefore acting on this section. - Inspiration — read
references/inspiration.mdbefore acting on this section.
Copy-paste-to-agent
Generate production-grade Apex (class + .cls-meta.xml) AND its test class (Test.cls +
.cls-meta.xml) as one unit. Test generation is mandatory, not optional. Bulkify all SOQL
and DML out of loops. Enforce CRUD/FLS via Schema.* checks or USER_MODE. Declare an explicit
sharing keyword on every class. Test with 251+ records to cross the 200-trigger boundary.
Use TestDataFactory — never inline record creation in @TestSetup. Use Assert.* class only —
never legacy System.assertEquals. After generation, fail-closed validate: compile dry-run,
then sf code-analyzer, then sf apex run test. Remediate sev0/sev1/sev2. Paste actual tool
output on the Compile / Analyzer / Testing report lines, or `<check>=unavailable: <reason>`
after attempting the fallback. Never treat a skipped or empty tool result as a pass.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/hand-off-to-sf-compound.md 699 B
- references/inspiration.md 1.4 KB
- references/phase-1-author-the-production-class.md 6.6 KB
- references/phase-2-author-the-test-class-mandatory-principle-2.md 8.5 KB
- references/phase-3-validate-mandatory-before-reporting-principle-2.md 4.8 KB
- references/phase-4-report.md 1.1 KB
- references/required-inputs-gather-or-infer-before-authoring.md 1.9 KB
- references/step-0-pre-implementation-research-parallel-principle-7.md 1.6 KB
- references/test-only-mode-apex-generate-test-for.md 657 B
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.
- 9d ago First seen · 49 lines · 214 tokens per session scan A 4d3f74e5dcda
apex-generate is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed 5d ago), licensed MIT. It adds 214 tokens to every session and 1,048 once invoked, about $0.0011 per session on Opus 5. 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 skills, from other repositories
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
prowler-test-api
Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).
python-sdk
Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.
convex-test
Generate convex-test tests for the app's Convex functions.
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.