design-custom-metadata

design-custom-metadata is a command for Claude Code from PranavNagrecha/AwesomeSalesforceSkills. It costs 0 tokens per session (496 once invoked), scanned A, original, no licence file.

A configuration design assistant that chooses between Salesforce custom metadata and two types of custom settings, then defines their fields and use.

In plain words
What is it for?
Use it to design reusable application settings, decide how they move between environments, and document how code or automation reads them.
Why use it?
It helps avoid storing configuration in the wrong Salesforce feature and clarifies what should be deployed or loaded separately.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the sfskills plugin — 12 skills, 69 commands shipped together , and of sfskills

Good fit Use it to design reusable application settings, decide how they move between environments, and document how code or automation reads them.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/pranavnagrecha/awesomesalesforceskills/design-custom-metadata
Install

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.

Clone the repo
git clone --depth 1 https://github.com/PranavNagrecha/AwesomeSalesforceSkills

Made for: Claude Code.

Or install sfskills, the plugin that ships this one along with the rest of its 12 skills, 69 commands.

Wrote 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.

agentmods badge for design-custom-metadata

README.md
[![agentmods](https://agentmods.dev/badge/commands/pranavnagrecha/awesomesalesforceskills/design-custom-metadata/github.svg)](https://agentmods.dev/commands/pranavnagrecha/awesomesalesforceskills/design-custom-metadata)
Your own site
<a href="https://agentmods.dev/commands/pranavnagrecha/awesomesalesforceskills/design-custom-metadata"><img src="https://agentmods.dev/badge/commands/pranavnagrecha/awesomesalesforceskills/design-custom-metadata/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.

agentmods 80×15 button for design-custom-metadata

Your own site · 80×15
<a href="https://agentmods.dev/commands/pranavnagrecha/awesomesalesforceskills/design-custom-metadata"><img src="https://agentmods.dev/badge/commands/pranavnagrecha/awesomesalesforceskills/design-custom-metadata.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 496 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00496
Opus 5 $0.00000 $0.00248
Sonnet 5 $0.00000 $0.00099
Haiku 4.5 $0.00000 $0.00050

Measured 8d ago against content hash e5ac5a11bb09, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

design-custom-metadata 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 8d 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.

commands/design-custom-metadata.md · 70 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

Changes

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.

  1. 8d ago First seen · 70 lines · 0 tokens per session scan A e5ac5a11bb09

Subscribe to this mod's changes

design-custom-metadata is a command published in the GitHub repository PranavNagrecha/AwesomeSalesforceSkills (17 stars, last pushed 8d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 496 tokens. 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-09-03.