async-apex

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

A command for creating, improving, or debugging asynchronous Apex code. Asynchronous code runs work later or in the background, including Batch, Queueable, Schedulable, and Future jobs.

In plain words
What is it for?
Use it to build a new async Apex class, refine an existing one, or diagnose and fix a bug.
Why use it?
It helps choose a suitable background-processing pattern and address concerns such as data volume, scheduled execution, web requests, and chained jobs.

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 a new async Apex class, refine an existing one, or diagnose and fix a bug.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/bhanu91221/sfdx-iq/async-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 async-apex

README.md
[![agentmods](https://agentmods.dev/badge/commands/bhanu91221/sfdx-iq/async-apex.svg)](https://agentmods.dev/commands/bhanu91221/sfdx-iq/async-apex)
Your own site
<a href="https://agentmods.dev/commands/bhanu91221/sfdx-iq/async-apex"><img src="https://agentmods.dev/badge/commands/bhanu91221/sfdx-iq/async-apex.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 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,707 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.00022 $0.02707
Opus 5 $0.00011 $0.01354
Sonnet 5 $0.00004 $0.00541
Haiku 4.5 $0.00002 $0.00271

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

Security

Grade A, and why

async-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/async-apex.md · 340 lines

How it starts

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

/async-apex

Work with asynchronous Apex patterns using --new, --refine, or --bug-fix.

Usage

/async-apex --new          Create a new async Apex class (Batch, Queueable, Schedulable, or Future)
/async-apex --refine       Modify an existing async class
/async-apex --bug-fix      Diagnose and fix a bug in async Apex code

--new: Create a New Async Class

Gather Requirements

Ask the user:

  1. What type? (Batch, Queueable, Schedulable, or @future method)
  2. What does it process? (object, business operation)
  3. What's the estimated data volume? (helps choose batch size)
  4. Does it need to make HTTP callouts?
  5. Should it chain to another async job after completion?

Choosing the Right Pattern

Pattern Use When
Batch Apex Processing large volumes (1,000+ records), scheduled or on-demand
Queueable Single async operation, needs callouts, can chain jobs
Schedulable Time-based execution (cron), typically kicks off a Batch
@future Legacy simple async — prefer Queueable for new code

Batch Apex Pattern

public class AccountSyncBatch implements Database.Batchable<SObject>, Database.Stateful {

    private Integer processedCount = 0;
    private List<String> errors = new List<String>();

    public Database.QueryLocator start(Database.BatchableContext bc) {
        // Use QueryLocator for large volumes — no LIMIT needed here
        return Database.getQueryLocator([
            SELECT Id, Name, SyncStatus__c
            FROM Account
            WHERE SyncStatus__c = 'Pending'
            ORDER BY CreatedDate ASC
        ]);
    }

    public void execute(Database.BatchableContext bc, List<Account> scope) {
        // Each execute() gets a FRESH set of governor limits
        List<Account> toUpdate = new List<Account>();
        for (Account acc : scope) {
            acc.SyncStatus__c = 'Complete';
            toUpdate.add(acc);
        }
        Database.SaveResult[] results = Database.update(toUpdate, false);
        for (Database.SaveResult sr : results) {
            if (!sr.isSuccess()) {
                errors.add(sr.getErrors()[0].getMessage());
            } else {
                processedCount++;
            }
        }
    }

    public void finish(Database.BatchableContext bc) {
        // Chain next job or send notification
        if (!errors.isEmpty()) {
            // Log or email errors
        }
    }
}

// Execute with default 200 scope
Database.executeBatch(new AccountSyncBatch());
// Execute with custom scope size
Database.executeBatch(new AccountSyncBatch(), 50); // smaller = more SOQL budget per execute

Read the full file on GitHub · 340 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 · 340 lines · 22 tokens per session scan A 6d0485c73771

Subscribe to this mod's changes

async-apex is a command published in the GitHub repository bhanu91221/sfdx-iq (2 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 2,707 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.