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/optimize-soql)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/optimize-soql"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/optimize-soql/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/optimize-soql"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/optimize-soql.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.00427 |
| Opus 5 | $0.00000 | $0.00214 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
optimize-soql 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 9d 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.
What it actually says
/optimize-soql — Find and fix SOQL anti-patterns
Wraps agents/soql-optimizer/AGENT.md. Scans a scope for queries-in-loops, non-selective WHEREs, missing security clauses, and SELECT-star patterns. Returns ranked fixes.
Step 1 — Collect inputs
Ask:
1. What scope should be analyzed?
File or folder path. Example: force-app/main/default/classes/AccountService.cls
or: force-app/main/default/classes/
2. Expected record count for any objects queried? (optional — escalates severity for LDV)
3. Target-org alias? (optional — enables live-org context)
Step 2 — Load the agent
Read agents/soql-optimizer/AGENT.md fully + every skill and template listed in its Mandatory Reads.
Step 3 — Execute
Follow the 5-step plan:
- Extract every SOQL query in scope
- Classify (query-in-loop, select-star, non-selective, no-security, etc.)
- Propose before/after fixes for P0 and P1 findings
- Recommend centralization if > 3 queries on the same sObject
- (Optional) org-side validation
Step 4 — Deliver
- Summary counts (files, queries, findings by severity)
- Findings table (file, line, severity, code, one-liner)
- Per-finding before/after code block for P0 and P1
- Centralization recommendation
- Citations
Step 5 — Recommend follow-ups
/refactor-apexon any class whose queries should move into aBaseSelectorsubclass./score-deploymentbefore shipping selector changes to production.
What this command does NOT do
- Does not modify files.
- Does not create custom indexes in the org.
- Does not attempt to rewrite
Database.query(<variable>)dynamic SOQL.
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.
- 9d ago First seen · 62 lines · 0 tokens per session scan A cd0991700b24
optimize-soql 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 427 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
init
Initialize configurations for Supabase local development.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
ingest
Manually add knowledge to the Weaviate store.
json.batch_delete
Delete multiple JSON documents or paths in one itemwise batch.
json.batch_get
Read multiple JSON values by document and path.
json.index.drop
Drop a JSON secondary index by name.