data-query

A tool for running Salesforce Object Query Language, or SOQL, queries to retrieve records from a Salesforce organization.

In plain words
What is it for?
Use it for normal record searches, counts, parent or child relationship queries, sorting, filtering, and result limits.
Why use it?
It avoids manually browsing records and supports relationships and filtering when a simple lookup is not enough.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/tsmztech/claude-code-plugins/data-query
Any agent
npx skills add tsmztech/claude-code-plugins --skill data-query
Clone the repo
git clone --depth 1 https://github.com/tsmztech/claude-code-plugins

Made for: Claude Code, Codex.

Per session 180 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,871 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00180 $0.03871
Opus 5 $0.00090 $0.01936
Sonnet 5 $0.00036 $0.00774
Haiku 4.5 $0.00018 $0.00387

Measured yesterday against content hash a249c2887a31, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

data-query 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 yesterday.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/count.js, scripts/query.js, scripts/subquery.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

salesforce-cli/skills/data-query/SKILL.md · 318 lines

How it starts

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

SOQL Query

Run any SOQL query against a connected Salesforce org. This skill handles all query types through dedicated scripts optimized for each pattern.

Prerequisites

You must be authenticated to a Salesforce org before running queries. If not authenticated, run the authentication script first.

Authentication

If the user is not authenticated or gets an auth error, run the authentication script:

node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --status

To authenticate interactively (opens browser):

node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --alias <alias>

To authenticate to a sandbox:

node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --alias <alias> --instance-url https://test.salesforce.com

See scripts/sf-auth.js --help for all authentication options.

Query Types & Scripts

This skill provides three scripts, one for each query pattern. Choose the right one based on what the user needs.

Note: For aggregate queries (SUM, AVG, MIN, MAX with GROUP BY / ROLLUP / CUBE / HAVING), use the salesforce-cli:aggregate-query skill instead.


1. Standard Query (includes child-to-parent dot notation)

Use for normal SELECT queries, including traversing parent relationships via dot notation.

node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "<SOQL>" [options]
Examples
# Simple query
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, Name FROM Account LIMIT 10"

# With WHERE clause
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, Name FROM Account WHERE Industry = 'Technology' AND AnnualRevenue > 1000000"

# Child-to-parent dot notation (up to 5 levels)
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, Name, Account.Name, Account.Owner.Name FROM Contact WHERE Account.Industry = 'Finance'"

# Custom relationship dot notation (__r instead of __c)
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, Broker__r.Name, Broker__r.Email FROM Property__c"

# ORDER BY, LIMIT, OFFSET
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, Name, CreatedDate FROM Account ORDER BY CreatedDate DESC LIMIT 20 OFFSET 10"

# Date literals
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, Name FROM Opportunity WHERE CloseDate = LAST_N_DAYS:30"

# LIKE operator with wildcards
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, Name FROM Account WHERE Name LIKE 'Acme%'"

# IN operator
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, Name FROM Account WHERE Industry IN ('Technology', 'Finance', 'Healthcare')"

# INCLUDES/EXCLUDES for multi-select picklists
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, Name FROM Lead WHERE LeadSource INCLUDES ('Web', 'Phone')"

# USING SCOPE
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, Name FROM Account USING SCOPE Mine"

# WITH SECURITY_ENFORCED
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, Name FROM Account WITH SECURITY_ENFORCED"

# TYPEOF for polymorphic relationships
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT TYPEOF What WHEN Account THEN Name, Phone WHEN Opportunity THEN Name, Amount ELSE Name END FROM Event"

# FIELDS() function
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT FIELDS(ALL) FROM Account LIMIT 200"
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT FIELDS(STANDARD) FROM Contact"
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT FIELDS(CUSTOM) FROM Opportunity LIMIT 200"

# FORMAT() and toLabel()
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, FORMAT(Amount), toLabel(StageName) FROM Opportunity LIMIT 5"

# convertCurrency() for multi-currency orgs
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, convertCurrency(Amount) FROM Opportunity"

# DISTANCE() and GEOLOCATION() for location-based queries
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, Name, BillingLatitude, BillingLongitude FROM Account WHERE DISTANCE(BillingAddress, GEOLOCATION(37.7749, -122.4194), 'mi') < 50 ORDER BY DISTANCE(BillingAddress, GEOLOCATION(37.7749, -122.4194), 'mi')"

# FOR VIEW / FOR REFERENCE / FOR UPDATE
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, Name FROM Account FOR VIEW"

# Against a specific org
node ${CLAUDE_PLUGIN_ROOT}/skills/data-query/scripts/query.js "SELECT Id, Name FROM Account LIMIT 5" --target-org myDevOrg

Read the full file on GitHub · 318 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. yesterday First seen · 318 lines · 180 tokens per session scan A a249c2887a31

Subscribe to this mod's changes

data-query is a skill published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 6mo ago), licensed MIT. It adds 180 tokens to every session and 3,871 once invoked, about $0.0009 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens