integration-apex

integration-apex is a command for Claude Code from bhanu91221/sfdx-iq. It costs 24 tokens per session (2,260 once invoked), scanned A, original, MIT.

A command for creating, improving, or fixing Salesforce Apex integrations. Apex is Salesforce's programming language, and the integrations can use REST or SOAP to exchange data with other systems.

In plain words
What is it for?
Use it to build or modify outbound callouts from Salesforce or inbound services called by another system. It supports new work, refinement, and bug fixing.
Why use it?
It structures the questions and implementation choices needed for Salesforce integrations. It helps account for authentication, retries, execution style, and the direction of communication.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the sfdx-iq plugin — 20 commands, 7 agents shipped together

Good fit Use it to build or modify outbound callouts from Salesforce or inbound services called by another system. It supports new work, refinement, and bug fixing.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/bhanu91221/sfdx-iq/integration-apex
Install

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.

Clone the repo
git clone --depth 1 https://github.com/bhanu91221/sfdx-iq

Made for: Claude Code.

Or install sfdx-iq, the plugin that ships this one along with the rest of its 20 commands, 7 agents.

Wrote 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.

agentmods badge for integration-apex

README.md
[![agentmods](https://agentmods.dev/badge/commands/bhanu91221/sfdx-iq/integration-apex/github.svg)](https://agentmods.dev/commands/bhanu91221/sfdx-iq/integration-apex)
Your own site
<a href="https://agentmods.dev/commands/bhanu91221/sfdx-iq/integration-apex"><img src="https://agentmods.dev/badge/commands/bhanu91221/sfdx-iq/integration-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.

agentmods 80×15 button for integration-apex

Your own site · 80×15
<a href="https://agentmods.dev/commands/bhanu91221/sfdx-iq/integration-apex"><img src="https://agentmods.dev/badge/commands/bhanu91221/sfdx-iq/integration-apex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,260 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.02260
Opus 5 $0.00012 $0.01130
Sonnet 5 $0.00005 $0.00452
Haiku 4.5 $0.00002 $0.00226

Measured 8d ago against content hash fa671c648970, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

integration-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 8d 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.

commands/integration-apex.md · 305 lines

How it starts

The opening of the file, as written. The whole thing — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/integration-apex

Work with Salesforce integration code — outbound callouts (REST/SOAP) and inbound web services — using --new, --refine, or --bug-fix.

Usage

/integration-apex --new          Create new integration Apex (callout class or inbound service)
/integration-apex --refine       Modify an existing integration class
/integration-apex --bug-fix      Diagnose and fix a bug in integration code

--new: Create New Integration Apex

Gather Requirements

Ask the user:

  1. Direction? Outbound callout (Salesforce calls external) or Inbound service (external calls Salesforce)?
  2. Protocol? REST or SOAP?
  3. Authentication method? OAuth 2.0, API Key, JWT, Named Credential?
  4. What operation? (sync account data, retrieve order status, POST event, etc.)
  5. Does it need retry logic? Circuit breaker?
  6. Synchronous or asynchronous execution context?

Outbound REST Callout Pattern

public with sharing class ExternalApiService {

    private static final String NAMED_CREDENTIAL = 'ExternalApi'; // Always use Named Credentials

    public static ExternalApiResponse syncAccount(Id accountId) {
        Account acc = [SELECT Id, Name, Industry FROM Account WHERE Id = :accountId WITH USER_MODE LIMIT 1];

        HttpRequest req = new HttpRequest();
        req.setEndpoint('callout:' + NAMED_CREDENTIAL + '/api/v1/accounts');
        req.setMethod('POST');
        req.setHeader('Content-Type', 'application/json');
        req.setHeader('Accept', 'application/json');
        req.setBody(JSON.serialize(new AccountPayload(acc)));
        req.setTimeout(30000); // 30 second timeout

        Http http = new Http();
        HttpResponse res = http.send(req);

        if (res.getStatusCode() == 200 || res.getStatusCode() == 201) {
            return (ExternalApiResponse) JSON.deserialize(res.getBody(), ExternalApiResponse.class);
        } else {
            throw new IntegrationException('API call failed: ' + res.getStatusCode() + ' ' + res.getBody());
        }
    }

    public class AccountPayload {
        public String name;
        public String industry;
        public AccountPayload(Account acc) {
            this.name = acc.Name;
            this.industry = acc.Industry;
        }
    }

    public class ExternalApiResponse {
        public String id;
        public String status;
    }

    public class IntegrationException extends Exception {}
}

Read the full file on GitHub · 305 lines

Changes

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.

  1. 8d ago First seen · 305 lines · 24 tokens per session scan A fa671c648970

Subscribe to this mod's changes

integration-apex is a command published in the GitHub repository bhanu91221/sfdx-iq (2 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 2,260 once invoked, about $0.0001 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.