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/bhanu91221/sfdx-iqWrote 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/bhanu91221/sfdx-iq/integration-apex)<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.
<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>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.00024 | $0.02260 |
| Opus 5 | $0.00012 | $0.01130 |
| Sonnet 5 | $0.00005 | $0.00452 |
| Haiku 4.5 | $0.00002 | $0.00226 |
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.
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:
- Direction? Outbound callout (Salesforce calls external) or Inbound service (external calls Salesforce)?
- Protocol? REST or SOAP?
- Authentication method? OAuth 2.0, API Key, JWT, Named Credential?
- What operation? (sync account data, retrieve order status, POST event, etc.)
- Does it need retry logic? Circuit breaker?
- 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 {}
}
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.
- 8d ago First seen · 305 lines · 24 tokens per session scan A fa671c648970
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.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
api-contract-review
Review an API contract (endpoints, request/response shapes, error codes, auth model) BEFORE implementation for naming consistency, versioning, pagination, idempotency, and alignment with existing endpoints. Distinct from review-hard (post-implementation risk) and repo-consistency-sweep (pattern matching on written…
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…