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 skills add ozgurkarahan/salesforce-meta-tool-identity-propagation --skill salesforce-crmgit clone --depth 1 https://github.com/ozgurkarahan/salesforce-meta-tool-identity-propagationWrote 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/ozgurkarahan/salesforce-meta-tool-identity-propagation/salesforce-crm)<a href="https://agentmods.dev/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/salesforce-crm"><img src="https://agentmods.dev/badge/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/salesforce-crm/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/ozgurkarahan/salesforce-meta-tool-identity-propagation/salesforce-crm"><img src="https://agentmods.dev/badge/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/salesforce-crm.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.00068 | $0.00774 |
| Opus 5.5 | $0.00027 | $0.00310 |
| Sonnet 5.5 | $0.00014 | $0.00155 |
| Haiku 4.5 | $0.00007 | $0.00077 |
Grade A, and why
salesforce-crm 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 today.
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce CRM
Workflow
- Identify the user only when needed. If the user says "my"/"me", reuse a UserId
already in this conversation; otherwise call
whoamionce. Filter withOwnerId = '<UserId>'orCreatedById = '<UserId>'. - Find the object. Skip for well-known standard objects (Account, Contact,
Opportunity, Case, Lead, Task, Event, User). Otherwise call
list_objects(filter=...)and use thename(API name), never thelabel. - Learn the fields.
- Reads: skip
describe_objectwhen you only need common fields (Id, Name, CreatedDate, OwnerId, LastModifiedDate) or fields already seen in this conversation. Otherwise usemode="slim"(types,referenceTo,childRelationships) ormode="names"to only validate names. - Writes:
describe_object(mode="full")is REQUIRED every time — picklists and validation rules change.
- Reads: skip
- Execute.
soql_queryfor exact filters, joins and aggregates.search_records(SOSL) when the object is unknown or for fuzzy keyword search.write_record(operation=create|update|upsert|delete).process_approval(action=Submit|Approve|Reject).
- Summarize in plain language. Never dump raw JSON.
SOQL rules
- Always include
LIMIT(default 20–50) unless the user explicitly asks for all rows.max_recordsdefaults to 100, cap 500. - API names are PascalCase:
Account,OpportunityLineItem,Custom_Field__c. - Parent fields via dot notation:
SELECT Name, Account.Name FROM Opportunity. - Child subqueries use the
relationshipNamefromchildRelationships, not the object name:SELECT Name, (SELECT Subject FROM Cases) FROM Account. - Open opportunities and open cases:
IsClosed = false. - Date literals:
CloseDate = NEXT_N_DAYS:90,CreatedDate = LAST_N_DAYS:30. - Quote string values with single quotes; escape embedded quotes.
Error recovery
INVALID_FIELD/MALFORMED_QUERY: the error containsavailableFields(name,type,referenceTo). Fix the query from it and retry immediately — do NOT calldescribe_objectagain. If the field is absent, the org hides it; look for a path through the parent'schildRelationships.INSUFFICIENT_ACCESS: the user lacks permission. Say which object/field and stop.ENTITY_IS_DELETED: tell the user the record was deleted.UNABLE_TO_LOCK_ROW: retry once.- Explain any error in plain language before retrying.
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.
- today First seen · 59 lines · 68 tokens per session scan A f23ee9bb751e
salesforce-crm is a skill published in the GitHub repository ozgurkarahan/salesforce-meta-tool-identity-propagation (4 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 774 once invoked, about $0.0003 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-10-17.
Other skills, from other repositories
claude-on-foundry
End-to-end assistant skill for the Claude on Foundry Starter Kit (Azure-Samples/claude). Walks customers through deploying, verifying, modifying, debugging, and tearing down a Claude model deployment on Microsoft Foundry using either the Bicep or Terraform IaC variant in this repo, with one-command guidance via azd…
api-security-design
Guidance for designing secure APIs on Azure - authentication, authorization, gateway controls, input validation, rate limiting, secret management, and runtime threat detection - aligned to OWASP API Security Top 10 and Azure API Management. WHEN: API security design, secure API, OWASP API Top 10, API authentication…
entra-id
Guidance for Microsoft Entra ID (formerly Azure AD) — cloud identity and access management and the control plane for Zero Trust. Covers tenant and identity model, authentication methods (passkeys, FIDO2, certificate-based), hybrid identity with Entra Connect or Cloud Sync, app registrations and consent governance…
defender-for-apis
Guidance for Microsoft Defender for APIs — a Defender for Cloud plan that discovers, prioritizes by risk, and protects APIs published in Azure API Management against threats and abuse. Covers onboarding, security findings, and threat detection. WHEN: Defender for APIs, API threat protection, secure APIs in API…
om-grounded-sql
Ground every query in the catalog before writing SQL; abstain when the catalog cannot ground it.
dashboard-authoring
Turn a recurring query template into a semantic-model + report definition, deterministically.