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 change-riskgit 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/change-risk)<a href="https://agentmods.dev/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/change-risk"><img src="https://agentmods.dev/badge/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/change-risk/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/change-risk"><img src="https://agentmods.dev/badge/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/change-risk.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.00046 | $0.00457 |
| Opus 5.5 | $0.00018 | $0.00183 |
| Sonnet 5.5 | $0.00009 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
change-risk 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
Change risk
Uses the salesforce-crm, servicenow-itsm and customer360-correlation skills.
Steps
- Changes — find the change(s) the user means, or upcoming ones:
query(table="change_request", query="short_descriptionLIKE<keyword>^ORdescriptionLIKE<keyword>", fields="number,short_description,description,type,risk,impact,state,start_date,end_date,company", limit=10). ServiceNow risk/impact:1High,2Medium/Moderate,3Low. - Exposure — identify affected customers from
companyand from systems named in the description (e.g. billing, payments, CRM, SSO). - Deals — open opportunities for those accounts closing within 60 days:
SELECT Account.Name, Name, Amount, StageName, CloseDate FROM Opportunity WHERE IsClosed = false AND Account.Name IN (...) AND CloseDate = NEXT_N_DAYS:60 ORDER BY CloseDate LIMIT 50. - Service context — open incidents for the same companies (a change landing on an already unstable customer is higher risk).
Rating
- High: change risk/impact High, or a deal ≥ $250K closes within 14 days of the window, or a P1/P2 incident is open for that customer.
- Medium: deals close within 60 days of the window, or risk/impact Medium.
- Low: otherwise.
Output
Per change: number, summary, window, risk/impact → affected accounts table (Account · Deal · Amount · Close date · Open incidents · Rating) → total pipeline exposed → recommendations (notify account owners, adjust the window, confirm the rollback plan). Do not modify the change request unless the user explicitly asks and confirms.
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 · 46 tokens per session scan A 589099aece79
change-risk is a skill published in the GitHub repository ozgurkarahan/salesforce-meta-tool-identity-propagation (4 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 457 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.