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 customer360-correlationgit 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/customer360-correlation)<a href="https://agentmods.dev/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/customer360-correlation"><img src="https://agentmods.dev/badge/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/customer360-correlation/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/customer360-correlation"><img src="https://agentmods.dev/badge/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/customer360-correlation.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.00059 | $0.00465 |
| Opus 5.5 | $0.00024 | $0.00186 |
| Sonnet 5.5 | $0.00012 | $0.00093 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
customer360-correlation 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.
What it actually says
Customer 360 correlation
Uses the salesforce-crm and servicenow-itsm skills for query rules.
Steps
- Tell the user the plan: what you will query in each system.
- Salesforce (one SOQL query where possible):
SELECT Id, Name, Industry, Type, AnnualRevenue, (SELECT Name, Amount, StageName, CloseDate FROM Opportunities WHERE IsClosed = false), (SELECT CaseNumber, Subject, Priority, Status FROM Cases WHERE IsClosed = false) FROM Account WHERE Name LIKE '%<company>%' LIMIT 5 - ServiceNow (one query per table, company names combined with
^OR): openincident, openproblem, upcomingchange_requestfor the company. - Correlate using the keys below and present one unified view.
Correlation keys
- Company: Salesforce
Account.Name↔ ServiceNowcompany.name. Treat legal-suffix variants as the same company ("Contoso" = "Contoso Ltd"). - Issue: a Salesforce Case and a ServiceNow Incident for the same company whose Subject/short_description share keywords (e.g. "API gateway", "SSO", "payment") and were opened within a few days of each other are likely the same issue seen from the customer side and the IT side.
Presentation
- Sections: Account snapshot · Open pipeline (total + deals) · Open cases · Open incidents/problems · Upcoming changes · Correlations · Suggested next steps.
- For every correlation, state what matched (company, keywords, dates) and how confident you are. Never invent a link.
- Lead with monetary amounts when pipeline is involved.
- If one system has no data for the company, say so explicitly rather than omitting it.
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 · 39 lines · 59 tokens per session scan A 5654f6e17145
customer360-correlation is a skill published in the GitHub repository ozgurkarahan/salesforce-meta-tool-identity-propagation (4 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 465 once invoked, about $0.0002 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…
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.
result-presentation
How to report a figure so it can be checked — number, definition, source, caveat.
dialect-postgres
PostgreSQL idioms the executor's guard accepts.
dialect-tsql
T-SQL idioms the executor's guard accepts, for Fabric Warehouse and SQL Server sources.