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.
npx agentmods add skills/tsmztech/claude-code-plugins/bulk-importnpx skills add tsmztech/claude-code-plugins --skill bulk-importgit clone --depth 1 https://github.com/tsmztech/claude-code-pluginsWhat 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 | $0.00103 | $0.01852 |
| Opus 5 | $0.00051 | $0.00926 |
| Sonnet 5 | $0.00021 | $0.00370 |
| Haiku 4.5 | $0.00010 | $0.00185 |
Grade A, and why
bulk-import 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 2d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bulk Import
Bulk insert, upsert, or update records from a CSV file using the Salesforce Bulk API v2. Designed for loading large datasets efficiently.
IMPORTANT — Safety Rules
Bulk operations modify many records at once. Follow these rules strictly:
- Always preview before executing. The script displays the first 3 rows and total row count. Confirm with the user before proceeding.
- Warn on large datasets. If the CSV has more than 1000 rows, explicitly warn the user about the scale of the operation.
- Recommend sandbox first. Suggest running bulk operations against a sandbox or developer org before production.
- Verify CSV headers. Ensure the CSV header row uses exact Salesforce API field names, not
display labels. Use the
salesforce-cli:describe-objectskill to verify.
Prerequisites
You must be authenticated to a Salesforce org before running bulk 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 running a bulk import, verify that CSV column headers match Salesforce API field names:
- Use
salesforce-cli:describe-objectto look up the correct API names for the target object. - Check field types — ensure CSV values match expected types (text, number, date, picklist).
- Check required fields — for insert operations, ensure all required fields (nillable: false, createable: true) are present in the CSV.
- For custom objects, verify the object exists using the
salesforce-cli:search-objectsskill.
What ships with it
1 file 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.
- 2d ago First seen · 185 lines · 103 tokens per session scan A f17109059d89
bulk-import is a skill published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 6mo ago), licensed MIT. It adds 103 tokens to every session and 1,852 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…