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.
git clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote 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/commands/banibratachatterjee/awesomesalesforceskills/design-custom-metadata)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/design-custom-metadata"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/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.
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/design-custom-metadata"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/design-custom-metadata.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.00000 | $0.00496 |
| Opus 5 | $0.00000 | $0.00248 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
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 11d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-custom-metadata — Design or audit Custom Metadata Types + Custom Settings
Wraps agents/custom-metadata-and-settings-designer/AGENT.md. Picks the right artifact (CMT vs List Custom Setting vs Hierarchy Custom Setting) and emits field design + usage guidance + deploy/load boundary.
Step 1 — Collect inputs
Ask the user:
1. Mode? design | audit
2. Target org alias (required for audit; optional for design)?
3. Scenario (for design)?
Options: feature-flag | env-config | rule-table | api-registry | tax-or-rate-table |
rounding-rules | text-catalog | other (describe)
4. Consumers? (apex | flow | formula | validation-rule | lwc)
5. Protection needs? (protected-from-subscribers | org-internal | public)
6. Expected record count? (< 50 | 50-500 | 500+)
Step 2 — Load the agent
Read agents/custom-metadata-and-settings-designer/AGENT.md + mandatory reads (admin/custom-metadata-types, admin/custom-settings, standards/decision-trees/configuration-storage-selection.md).
Step 3 — Execute the plan
- Classify scenario against decision tree.
- Pick CMT vs List vs Hierarchy Custom Setting (cite the branch).
- Design fields + labels + API names per
templates/admin/naming-conventions.md. - Produce usage snippets for each consumer (Apex CMT query, Flow Get Records, formula references).
- Emit deploy-vs-data-load boundary (CMT = metadata, Custom Setting = data).
Step 4 — Deliver the output
- Summary + confidence
- Decision (with decision-tree branch cited)
- Field design
- Usage snippets per consumer
- Deploy/load boundary
- Audit findings (audit mode)
- Process Observations
- Citations
Step 5 — Recommend follow-ups
/architect-permsfor CMT Record Manager permissions/design-objectif the use case is actually a business entity, not configuration/refactor-apexif existing hardcoded rules should move to CMT
What this command does NOT do
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.
- 11d ago First seen · 70 lines · 0 tokens per session scan A e5ac5a11bb09
design-custom-metadata is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. 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-08-31.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
api-contract-review
Review an API contract (endpoints, request/response shapes, error codes, auth model) BEFORE implementation for naming consistency, versioning, pagination, idempotency, and alignment with existing endpoints. Distinct from review-hard (post-implementation risk) and repo-consistency-sweep (pattern matching on written…
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.