Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add tsmztech/claude-code-plugins/plugin install salesforce-cliWrote 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/skills/tsmztech/claude-code-plugins/dml-operations)<a href="https://agentmods.dev/skills/tsmztech/claude-code-plugins/dml-operations"><img src="https://agentmods.dev/badge/skills/tsmztech/claude-code-plugins/dml-operations/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/skills/tsmztech/claude-code-plugins/dml-operations"><img src="https://agentmods.dev/badge/skills/tsmztech/claude-code-plugins/dml-operations.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.00108 | $0.02329 |
| Opus 5.5 | $0.00043 | $0.00932 |
| Sonnet 5.5 | $0.00022 | $0.00466 |
| Haiku 4.5 | $0.00011 | $0.00233 |
Grade A, and why
dml-operations 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 2mo 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DML Operations
Insert, update, and upsert single records in a connected Salesforce org. This skill provides three scripts for different DML patterns: insert, update by Id, and upsert by external ID.
This skill does NOT support delete operations. For bulk operations from CSV files, use the
salesforce-cli:bulk-importskill.
IMPORTANT — Safety Rules
DML operations modify live data in Salesforce. Follow these rules strictly:
- Always confirm before executing. Before running ANY DML script, repeat back to the user: the operation type, the target object, and the exact field values. Wait for explicit confirmation.
- Never run DML speculatively. Every execution must be intentional and confirmed by the user.
- Recommend sandbox first. When possible, suggest the user run DML operations against a sandbox or developer org before production.
Prerequisites
You must be authenticated to a Salesforce org before running DML operations. 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.
Field Name Resolution
Before executing any DML operation, always verify field API names using the salesforce-cli:describe-object skill:
- When the user provides natural language field names (e.g., "phone number", "annual revenue"),
use
salesforce-cli:describe-objectto resolve them to the correct API names (e.g.,Phone,AnnualRevenue). - Check required fields — use
salesforce-cli:describe-objectto see which fields arenillable: falseandcreateable: true(for insert) orupdateable: true(for update). The insert will fail if required fields are missing. - Verify picklist values — if the user wants to set a picklist field, use
salesforce-cli:describe-objectwith--field <fieldName>to see valid picklist values. - Check field types — ensure the user's value matches the field type (e.g., don't pass a string to a number field).
- For custom objects, verify the object exists using
salesforce-cli:search-objectsskill before attempting DML.
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.
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.
- 2mo ago First seen · 213 lines · 108 tokens per session scan A a8c267896421
dml-operations is a skill published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 108 tokens to every session and 2,329 once invoked, about $0.0004 per session on Opus 5.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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…