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/create-objectnpx skills add tsmztech/claude-code-plugins --skill create-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.00107 | $0.01931 |
| Opus 5 | $0.00053 | $0.00966 |
| Sonnet 5 | $0.00021 | $0.00386 |
| Haiku 4.5 | $0.00011 | $0.00193 |
Grade A, and why
create-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 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Salesforce Custom Object
Guide the user through creating a new custom object in their Salesforce org. This is a conversational skill — gather all required information through questions before executing.
Workflow
User triggers skill
├── 1. Understand purpose & name — ask what the object is for, get label & API name
├── 2. Check for duplicates — run search-objects.js BEFORE gathering detailed settings
│ ├── Exact match found → STOP, tell user the object exists
│ ├── Similar objects found → show them, ask user to confirm proceed or pick a different name
│ └── No matches → proceed to gather settings
├── 3. Gather object settings — ask remaining questions (see below)
├── 4. Confirm all settings — show summary, ask for confirmation
├── 5. Create the object — run create-object.js
├── 6. Report result — show success/failure
└── 7. Offer next step — ask if they want to create fields now
Phase 1: Understand Purpose & Name
Start by asking the user what the object is for. This context helps you:
- Suggest a good label and API name
- Recommend appropriate settings (e.g., enable reports for trackable entities)
- Suggest relevant fields later
If the user already provided a label or description in their message (via $ARGUMENTS),
acknowledge it.
Get at minimum these before proceeding to the duplicate check:
| Setting | What to ask | Default |
|---|---|---|
| Label | "What should the object be called?" | From user input |
| Plural Label | "What's the plural form?" | Label + "s" |
| API Name | Suggest one derived from label, ask to confirm | Derived from label |
Phase 2: Check for Duplicates
Once you have the API name, immediately check for duplicates before gathering any more settings. This avoids wasting the user's time if the object already exists.
Step 1 — Search for similar objects (both standard and custom):
node ${CLAUDE_PLUGIN_ROOT}/scripts/search-objects.js "<ObjectName>" [--target-org <alias>]
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 · 217 lines · 107 tokens per session scan A 509855654cbf
create-object is a skill published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 6mo ago), licensed MIT. It adds 107 tokens to every session and 1,931 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.
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…