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/search-objectsnpx skills add tsmztech/claude-code-plugins --skill search-objectsgit 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.00074 | $0.00823 |
| Opus 5 | $0.00037 | $0.00411 |
| Sonnet 5 | $0.00015 | $0.00165 |
| Haiku 4.5 | $0.00007 | $0.00082 |
Grade A, and why
search-objects 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.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Salesforce Objects
Search for Salesforce standard and custom objects by name or label pattern. Returns matching objects with their API name, label, type (standard/custom), and queryability.
Prerequisites
You must be authenticated to a Salesforce org before searching objects. 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 ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --help for all authentication options.
Searching Objects
Basic usage
Search for objects matching a pattern:
node ${CLAUDE_PLUGIN_ROOT}/skills/search-objects/scripts/search.js $ARGUMENTS
Examples
# Search for objects containing "Account"
node ${CLAUDE_PLUGIN_ROOT}/skills/search-objects/scripts/search.js Account
# Multi-term search (finds WorkOrder, WorkOrderLineItem, etc.)
node ${CLAUDE_PLUGIN_ROOT}/skills/search-objects/scripts/search.js "Order Work"
# Search against a specific org
node ${CLAUDE_PLUGIN_ROOT}/skills/search-objects/scripts/search.js Case --target-org myDevOrg
# Only custom objects
node ${CLAUDE_PLUGIN_ROOT}/skills/search-objects/scripts/search.js Invoice --custom-only
# Only standard objects
node ${CLAUDE_PLUGIN_ROOT}/skills/search-objects/scripts/search.js Account --standard-only
# Only queryable objects
node ${CLAUDE_PLUGIN_ROOT}/skills/search-objects/scripts/search.js Order --queryable
# Show more results
node ${CLAUDE_PLUGIN_ROOT}/skills/search-objects/scripts/search.js "" --limit 100
# Get raw JSON output
node ${CLAUDE_PLUGIN_ROOT}/skills/search-objects/scripts/search.js Account --raw
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.
- yesterday First seen · 102 lines · 74 tokens per session scan A 964821e560c4
search-objects is a skill published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 6mo ago), licensed MIT. It adds 74 tokens to every session and 823 once invoked, about $0.0004 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.
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…
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…
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…
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…
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…