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/async-apex)<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>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.00022 | $0.02707 |
| Opus 5 | $0.00011 | $0.01354 |
| Sonnet 5 | $0.00004 | $0.00541 |
| Haiku 4.5 | $0.00002 | $0.00271 |
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.
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:
- What type? (Batch, Queueable, Schedulable, or @future method)
- What does it process? (object, business operation)
- What's the estimated data volume? (helps choose batch size)
- Does it need to make HTTP callouts?
- 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
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 · 340 lines · 22 tokens per session scan A 6d0485c73771
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.
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…