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/forcedotcom/sf-skills/platform-metadata-api-context-getnpx skills add forcedotcom/sf-skills --skill platform-metadata-api-context-getgit clone --depth 1 https://github.com/forcedotcom/sf-skillsWrote 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/forcedotcom/sf-skills/platform-metadata-api-context-get)<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/platform-metadata-api-context-get"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/platform-metadata-api-context-get.svg" alt="Measured on agentmods" 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.00215 | $0.05404 |
| Opus 5 | $0.00108 | $0.02702 |
| Sonnet 5 | $0.00043 | $0.01081 |
| Haiku 4.5 | $0.00021 | $0.00540 |
Grade A, and why
platform-metadata-api-context-get 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 — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce Metadata API Skill
This skill provides comprehensive documentation for all 604 Salesforce Metadata API types. Use this skill to create, understand, and modify Salesforce metadata XML files in your Salesforce DX projects.
Overview
The Salesforce Metadata API allows you to retrieve, deploy, create, update, or delete customizations for your org. This skill gives you access to detailed documentation for each metadata type, including:
- Field definitions and data types
- Required vs. optional fields
- WSDL schema definitions
- Sample XML structures
- File naming conventions
- Directory locations in Salesforce DX projects
How to Use This Skill
CRITICAL: Section-Specific Consumption
ALWAYS consume only the specific sections you need from JSON files, NOT entire files.
CRITICAL: For assets/metadata_api/*.json files, always use jq or programmatic JSON parsing to extract only the specific sections you need. Do not load these files whole via Read, cat, read_file, or any other tool that injects the complete file — they contain verbose WSDL segments and other sections that waste 60-80% of tokens. (Loading small files like this SKILL.md or the index table with Read is fine; the rule applies specifically to the large metadata-type JSON files.)
Each JSON file contains multiple sections (fields, description, wsdl_segment, etc.). Most use cases only require 1-2 sections:
- For field definitions: Load only the
fieldssection - For understanding purpose: Load only the
descriptionsection - For XML examples: Load only the
declarative_metadata_sample_definitionsection - Skip by default:
wsdl_segment(verbose schema),file_information,directory_location
This reduces token consumption by 60-80% per file.
Quick Start
To get information about a specific metadata type:
- Section-specific (BEST): "Show me only the 'fields' section from CustomObject.json"
- Multiple sections: "Show me 'fields' and 'description' from Flow.json"
- Avoid loading entire files: Don't ask for "the CustomObject metadata type" - specify sections
What ships with it
60 files 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.
- assets/metadata_api/AccountingFieldMapping.json 4.3 KB
- assets/metadata_api/AccountingModelConfig.json 4.9 KB
- assets/metadata_api/AccountingSettings.json 2.9 KB
- assets/metadata_api/AccountInsightsSettings.json 1.1 KB
- assets/metadata_api/AccountIntelligenceSettings.json 2.4 KB
- assets/metadata_api/AccountPlanObjMeasCalcDef.json 5.8 KB
- assets/metadata_api/AccountPlanSettings.json 1.4 KB
- assets/metadata_api/AccountRelationshipShareRule.json 3.6 KB
- assets/metadata_api/AccountSettings.json 5.6 KB
- assets/metadata_api/ActionableListDefinition.json 11 KB
- assets/metadata_api/ActionLinkGroupTemplate.json 12 KB
- assets/metadata_api/ActionOverride.json 17 KB
- assets/metadata_api/ActionPlanTemplate.json 15 KB
- assets/metadata_api/ActionsSettings.json 2.4 KB
- assets/metadata_api/ActivationPlatform.json 4.4 KB
- assets/metadata_api/ActivationPlatformActvAttr.json 232 B
- assets/metadata_api/ActivationPlatformField.json 2.0 KB
- assets/metadata_api/ActivitiesSettings.json 13 KB
- assets/metadata_api/ActvPfrmDataConnectorS3.json 1.3 KB
- assets/metadata_api/ActvPlatformAdncIdentifier.json 1.9 KB
- assets/metadata_api/ActvPlatformFieldValue.json 1.8 KB
- assets/metadata_api/AddressSettings.json 9.3 KB
- assets/metadata_api/AdvAccountForecastSet.json 14 KB
- assets/metadata_api/AffinityScoreDefinition.json 5.6 KB
- assets/metadata_api/AgentforceForDevelopersSettings.json 1.7 KB
- assets/metadata_api/AgentPlatformSettings.json 1.3 KB
- assets/metadata_api/AIApplication.json 1.4 KB
- assets/metadata_api/AIApplicationConfig.json 2.1 KB
- assets/metadata_api/AiAuthoringBundle.json 3.9 KB
- assets/metadata_api/AiEvaluationDefinition.json 10.0 KB
- assets/metadata_api/AiPluginUtteranceDef.json 6.5 KB
- assets/metadata_api/AIReplyRecommendationsSettings.json 2.5 KB
- assets/metadata_api/AIScoringModelDefinition.json 7.0 KB
- assets/metadata_api/AIUsecaseDefinition.json 19 KB
- assets/metadata_api/AllOrNoneHeader.json 581 B
- assets/metadata_api/AnalyticsDashboard.json 33 KB
- assets/metadata_api/AnalyticSnapshot.json 6.2 KB
- assets/metadata_api/AnalyticsSettings.json 39 KB
- assets/metadata_api/AnalyticsVisualization.json 17 KB
- assets/metadata_api/AnalyticsWorkspace.json 5.1 KB
- assets/metadata_api/AnimationRule.json 4.3 KB
- assets/metadata_api/ApexClass.json 6.0 KB
- assets/metadata_api/ApexComponent.json 3.8 KB
- assets/metadata_api/ApexEmailNotifications.json 2.8 KB
- assets/metadata_api/ApexPage.json 5.2 KB
- assets/metadata_api/ApexSettings.json 7.9 KB
- assets/metadata_api/ApexTestSuite.json 2.1 KB
- assets/metadata_api/ApexTrigger.json 4.3 KB
- assets/metadata_api/AppAnalyticsSettings.json 2.0 KB
- assets/metadata_api/AppExperienceSettings.json 1.7 KB
- assets/metadata_api/AppFrameworkTemplateBundle.json 3.6 KB
- assets/metadata_api/AppMenu.json 954 B
- assets/metadata_api/AppointmentAssignmentPolicy.json 3.3 KB
- assets/metadata_api/AppointmentSchedulingPolicy.json 7.5 KB
- assets/metadata_api/ApprovalProcess.json 29 KB
- assets/metadata_api/ArticleType_CustomField.json 4.5 KB
- assets/metadata_api/ArticleType_Layout.json 3.0 KB
- assets/metadata_api/ArticleType.json 5.3 KB
- assets/metadata_api/AssessmentQuestion.json 4.9 KB
- assets/metadata_api/AssessmentQuestionSet.json 1.8 KB
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 · 475 lines · 215 tokens per session scan A d3e3b5b0ee9f
platform-metadata-api-context-get is a skill published in the GitHub repository forcedotcom/sf-skills (964 stars, last pushed yesterday), licensed Apache-2.0. It adds 215 tokens to every session and 5,404 once invoked, about $0.0011 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…