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/build-apex)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/build-apex"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/build-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/commands/banibratachatterjee/awesomesalesforceskills/build-apex"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/build-apex.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.00492 |
| Opus 5 | $0.00000 | $0.00246 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
build-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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/build-apex — Generate an Apex scaffold for any canonical surface
Wraps agents/apex-builder/AGENT.md. Produces Apex class(es) + test class that conform to templates/apex/ (TriggerHandler, BaseService, BaseSelector, ApplicationLogger, SecurityUtils, HttpClient).
Step 1 — Collect inputs
Ask the user:
1. What Apex surface do you need? (trigger+handler | service | selector | domain |
controller | batch | queueable | schedulable | invocable | rest | soap |
pe-subscriber | cdc-subscriber | iterator | async-continuation)
2. Primary sObject or functional area?
Example: "Account", "Order fulfillment", "/external/billing endpoint"
3. Description of behavior (3+ sentences — drives field/method design)?
4. Test-class strategy? (default: TestDataFactory + positive/negative/bulk)
If the description is under 3 sentences or the surface is ambiguous, STOP and clarify.
Step 2 — Load the agent
Read agents/apex-builder/AGENT.md + all mandatory reads (apex-trigger-framework, apex-service-selector-domain, apex-security-crud-fls, apex-bulkification, apex-testing-patterns, plus templates under templates/apex/).
Step 3 — Execute the plan
Follow the agent's plan: choose surface → pick template → generate scaffold → wire SecurityUtils + ApplicationLogger → generate matching test class.
Step 4 — Deliver the output
- Summary + confidence
- Apex class(es) (fenced ```apex blocks, one per file)
- Matching test class (≥ 90% coverage target, bulk + negative cases)
- Deployment order + any dependency notes
- Process Observations
- Citations
Step 5 — Recommend follow-ups
/gen-testsif coverage needs deepening/optimize-soqlif the scaffold issues SOQL/scan-securitybefore deploy/consolidate-triggersif a trigger scaffold overlaps an existing trigger
What this command does NOT do
- Does not deploy.
- Does not run tests against a live org.
- Does not modify existing Apex — use
/refactor-apexfor that.
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 · 65 lines · 0 tokens per session scan A 8a31bbef26f9
build-apex 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 492 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
cloudflare-durable-objects:setup
Interactive Durable Objects project initialization. Scaffolds new DO project with proper bindings, migrations, and boilerplate code.
dare-laravel-api
Padrões DARE para APIs REST em Laravel 11 + PHP 8.3. Strict Types, FormRequests, Services, Resources, Repositories, Eloquent + casts, tratamento global de exceções, testes Pest, PHPStan/Larastan nível 8.
load-test
Generate load testing scenarios (k6/Locust) from API contracts with realistic traffic patterns.
setup
Connect this workspace to Scalix Cloud — verify the API key, test the MCP endpoint, and optionally install the CLI.
ads_canonical-models-validate
Verify canonical models compile, tests pass, deprecation notices in place.
apim-contract-diff
Execute the apim contract diff workflow with deterministic validation and redacted output.