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 Jaganpro/sf-skills --skill sf-apexgit clone --depth 1 https://github.com/Jaganpro/sf-skillsWrote 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/jaganpro/sf-skills/sf-apex)<a href="https://agentmods.dev/skills/jaganpro/sf-skills/sf-apex"><img src="https://agentmods.dev/badge/skills/jaganpro/sf-skills/sf-apex/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/jaganpro/sf-skills/sf-apex"><img src="https://agentmods.dev/badge/skills/jaganpro/sf-skills/sf-apex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk 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.00094 | $0.01888 |
| Opus 5 | $0.00047 | $0.00944 |
| Sonnet 5 | $0.00019 | $0.00378 |
| Haiku 4.5 | $0.00009 | $0.00189 |
Grade A, and why
sf-apex 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 11d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sf-apex: Salesforce Apex Code Generation and Review
Use this skill when the user needs production Apex: new classes, triggers, selectors, services, async jobs, invocable methods, test classes, or evidence-based review of existing .cls / .trigger code.
When This Skill Owns the Task
Use sf-apex when the work involves:
- Apex class generation or refactoring
- trigger design and trigger-framework decisions
@InvocableMethod, Queueable, Batch, Schedulable, or test-class work- review of bulkification, sharing, security, testing, or maintainability
Delegate elsewhere when the user is:
- editing LWC JavaScript / HTML / CSS → sf-lwc
- building Flow XML or Flow orchestration → sf-flow
- writing SOQL only → sf-soql
- deploying or validating metadata to orgs → sf-deploy
Required Context to Gather First
Ask for or infer:
- class type: trigger, service, selector, batch, queueable, schedulable, invocable, test
- target object(s) and business goal
- whether code is net-new, refactor, or fix
- org / API constraints if known
- expected test coverage or deployment target
Before authoring, inspect the project shape:
- existing classes / triggers
- current trigger framework or handler pattern
- related tests, flows, and selectors
- whether TAF is already in use
Recommended Workflow
1. Discover local architecture
Check for:
- existing trigger handlers / frameworks
- service-selector-domain conventions
- related tests and data factories
- invocable or async patterns already used in the repo
2. Choose the smallest correct pattern
| Need | Preferred pattern |
|---|---|
| simple reusable logic | service class |
| query-heavy data access | selector |
| single object trigger behavior | one trigger + handler / TAF action |
| Flow needs complex logic | @InvocableMethod |
| background processing | Queueable by default |
| very large datasets | Batch Apex or Database.Cursor patterns |
| repeatable verification | dedicated test class + test data factory |
What ships with it
36 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.
- assets/apex-class.cls 406 B
- assets/batch.cls 3.8 KB
- assets/invocable-method.cls 9.3 KB
- assets/queueable.cls 1.8 KB
- assets/selector.cls 3.2 KB
- assets/service.cls 4.4 KB
- assets/test-class.cls 2.0 KB
- assets/test-data-factory.cls 3.4 KB
- assets/trigger-action.cls 922 B
- assets/trigger.trigger 349 B
- CREDITS.md 4.3 KB
- hooks/scripts/apex-lsp-validate.py 8.6 KB runs code
- hooks/scripts/llm_pattern_validator.py 15 KB runs code
- hooks/scripts/post-tool-validate.py 17 KB runs code
- hooks/scripts/prettier-format.py 3.4 KB runs code
- hooks/scripts/validate_apex.py 7.9 KB runs code
- README.md 2.9 KB
- references/anti-patterns.md 19 KB
- references/automation-density-guide.md 8.7 KB
- references/best-practices.md 14 KB
- references/bulkification-guide.md 19 KB
- references/code-review-checklist.md 6.1 KB
- references/code-smells-guide.md 16 KB
- references/design-patterns.md 32 KB
- references/flow-integration.md 16 KB
- references/llm-anti-patterns.md 19 KB
- references/naming-conventions.md 5.4 KB
- references/patterns-deep-dive.md 24 KB
- references/security-guide.md 17 KB
- references/security-quick-reference.md 6.5 KB
- references/solid-principles.md 10 KB
- references/testing-guide.md 11 KB
- references/testing-patterns.md 22 KB
- references/triangle-pattern.md 9.2 KB
- references/trigger-actions-framework.md 11 KB
- references/troubleshooting.md 18 KB
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.
- 11d ago First seen · 229 lines · 94 tokens per session scan A 9def71e9d8ab
sf-apex is a skill published in the GitHub repository Jaganpro/sf-skills (423 stars, last pushed 4mo ago), licensed MIT. It adds 94 tokens to every session and 1,888 once invoked, about $0.0005 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-30.
Other skills, from other repositories
platform-apex-generate
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill…
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
api-contract-review
Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.
principle-model-the-domain
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.
api-reviewer
A review of an API contract, the agreed description of how software systems exchange requests, responses, events, or files.