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/describe-objectnpx skills add tsmztech/claude-code-plugins --skill describe-objectgit 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.00067 | $0.00841 |
| Opus 5 | $0.00034 | $0.00420 |
| Sonnet 5 | $0.00013 | $0.00168 |
| Haiku 4.5 | $0.00007 | $0.00084 |
Grade A, and why
describe-object 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Describe Salesforce Object
Get detailed schema metadata for any Salesforce object — standard or custom — including all fields, relationships, field properties, and picklist values.
Prerequisites
You must be authenticated to a Salesforce org before describing 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
For CI/CD (JWT flow):
node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --method jwt --client-id <id> --jwt-key-file <path> --username <user>
To set a default org:
node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --set-default <alias>
See scripts/sf-auth.js --help for all authentication options.
Describing an Object
Basic usage
Describe a standard or custom object:
node ${CLAUDE_PLUGIN_ROOT}/skills/describe-object/scripts/describe.js $ARGUMENTS
Examples
# Describe Account object
node ${CLAUDE_PLUGIN_ROOT}/skills/describe-object/scripts/describe.js Account
# Describe against a specific org
node ${CLAUDE_PLUGIN_ROOT}/skills/describe-object/scripts/describe.js Contact --target-org myDevOrg
# Show only fields table
node ${CLAUDE_PLUGIN_ROOT}/skills/describe-object/scripts/describe.js Opportunity --fields-only
# Inspect a single field in detail
node ${CLAUDE_PLUGIN_ROOT}/skills/describe-object/scripts/describe.js Account --field Industry
# Show only relationships
node ${CLAUDE_PLUGIN_ROOT}/skills/describe-object/scripts/describe.js Case --relationships
# Get raw JSON output
node ${CLAUDE_PLUGIN_ROOT}/skills/describe-object/scripts/describe.js Custom_Object__c --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.
- 2d ago First seen · 105 lines · 67 tokens per session scan A db58165ce9b6
describe-object is a skill published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 6mo ago), licensed MIT. It adds 67 tokens to every session and 841 once invoked, about $0.0003 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.