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 revenue-at-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/revenue-at-risk)<a href="https://agentmods.dev/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/revenue-at-risk"><img src="https://agentmods.dev/badge/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/revenue-at-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/revenue-at-risk"><img src="https://agentmods.dev/badge/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/revenue-at-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.00059 | $0.00437 |
| Opus 5.5 | $0.00024 | $0.00175 |
| Sonnet 5.5 | $0.00012 | $0.00087 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
revenue-at-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
Revenue at risk
Uses the salesforce-crm, servicenow-itsm and customer360-correlation skills.
Steps
- Incidents — one ServiceNow query:
query(table="incident", query="priority<=2^state<6^ORDERBYpriority", fields="number,short_description,priority,state,company,opened_at", limit=50). If an incident has no company, infer it fromshort_description/descriptiononly when the name is explicit, and say you inferred it. - Affected companies — distinct company names from step 1.
- Pipeline — one SOQL query for all of them:
SELECT Account.Name, Name, Amount, StageName, CloseDate FROM Opportunity WHERE IsClosed = false AND Account.Name IN ('A','B',...) ORDER BY Amount DESC LIMIT 100 - Compute per account: open pipeline total, number of P1 and P2 incidents, nearest close date.
- Rank accounts by risk: P1 before P2, then pipeline amount, then nearest close date.
Output
- Start with the headline: total pipeline at risk and the number of accounts.
- Table: Account · Pipeline at risk · P1 · P2 · Nearest close date · Key incident(s).
- Then 2–3 recommended actions (e.g. escalate the incident tied to the largest deal closing soonest).
- Format amounts as currency (e.g. $1.2M, $450K). Only show totals computed from records, never untraceable estimates.
- If no high-priority incidents are open, say so and stop.
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 · 36 lines · 59 tokens per session scan A 9ea6b883d0f2
revenue-at-risk 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 437 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.