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-devWrote 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/create-field)<a href="https://agentmods.dev/skills/tsmztech/claude-code-plugins/create-field"><img src="https://agentmods.dev/badge/skills/tsmztech/claude-code-plugins/create-field/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/create-field"><img src="https://agentmods.dev/badge/skills/tsmztech/claude-code-plugins/create-field.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.00120 | $0.03466 |
| Opus 5.5 | $0.00048 | $0.01386 |
| Sonnet 5.5 | $0.00024 | $0.00693 |
| Haiku 4.5 | $0.00012 | $0.00347 |
Grade A, and why
create-field 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 — 438 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Salesforce Custom Field
Guide the user through creating a custom field on a Salesforce object. This is a conversational skill — gather all required information through questions before deploying.
Workflow
User triggers skill
├── 1. Identify target object — which object gets the new field?
├── 2. Choose field type — present the type list, get user's choice
├── 3. Check for duplicates — run describe-object.js BEFORE gathering details
│ ├── Exact match found → STOP, tell user the field exists
│ ├── Similar fields found → show them, ask user to confirm or pick a different name
│ └── No matches → proceed
├── 4. Gather field details — type-specific settings (see tables below)
├── 5. Field-level security — ask which profiles/permission sets should have access
├── 6. Page layout — ask if the field should be added to page layouts
├── 7. Confirm all settings — show summary, ask for confirmation
├── 8. Create the field — run create-field.js
├── 9. Report result — show success/failure
└── 10. Offer next step — ask if they want to create another field
Phase 1: Identify Target Object
Ask which object the field should be created on. If the user already specified it
(via $ARGUMENTS or earlier context), confirm it.
Describe the object to verify it exists and see its existing fields:
node ${CLAUDE_PLUGIN_ROOT}/scripts/describe-object.js <ObjectApiName> --fields-only [--target-org <alias>]
This gives you the full field list, which helps avoid duplicates and informs naming.
Phase 2: Choose Field Type
Present the available field types. Group them logically:
Basic Data Types:
| Type | Description |
|---|---|
| Text | Single-line text (up to 255 chars) |
| Text Area | Multi-line plain text (255 chars) |
| Text Area (Long) | Large plain text (up to 131,072 chars) |
| Text Area (Rich) | Rich text with formatting (up to 131,072 chars) |
| Number | Numeric value with decimals |
| Currency | Money value with currency symbol |
| Percent | Percentage value |
| Checkbox | True/false toggle |
| Date | Date only |
| Date/Time | Date and time |
| Time | Time only |
| Email address (validated format) | |
| Phone | Phone number |
| URL | Web address (displayed as link) |
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.
- 2mo ago First seen · 438 lines · 120 tokens per session scan A 79346eb4b8aa
create-field is a skill published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 120 tokens to every session and 3,466 once invoked, about $0.0005 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…