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 servicenow-itsmgit 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/servicenow-itsm)<a href="https://agentmods.dev/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/servicenow-itsm"><img src="https://agentmods.dev/badge/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/servicenow-itsm/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/servicenow-itsm"><img src="https://agentmods.dev/badge/skills/ozgurkarahan/salesforce-meta-tool-identity-propagation/servicenow-itsm.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.00061 | $0.00681 |
| Opus 5.5 | $0.00024 | $0.00272 |
| Sonnet 5.5 | $0.00012 | $0.00136 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
servicenow-itsm 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ServiceNow ITSM
Workflow
- Pick the table. Common tables need no lookup:
incident,problem,change_request,sc_req_item,sysapproval_approver,core_company. Otherwise calldiscover(filter=...)once. - Learn the fields.
- Reads: skip
discover(table=...)when the standard fields below are enough. Usemode="names"to validate names only;mode="compact"(default) for types and references. - Writes:
discover(table=..., include_choices=True)is REQUIRED first. - If
discoverreturns 403, fall back to the standard fields.
- Reads: skip
- Query with
query(table, query, fields, limit). - Summarize in plain language. Never dump raw JSON.
Standard fields: number, short_description, description, priority, state, urgency, impact, category, assignment_group, assigned_to, company, opened_at, sys_created_on.
Change requests add: type, risk, start_date, end_date.
Query rules
- ALWAYS pass
fields=with only the columns you need. - Encoded query syntax:
field=value,fieldLIKEvalue,fieldSTARTSWITHvalue,field!=value,field>value,fieldINa,b,fieldISEMPTY; AND^, OR^OR, sort^ORDERBYfield/^ORDERBYDESCfield. - Priority:
1Critical (P1),2High (P2),3Moderate,4Low. Incident state:1New,2In Progress,3On Hold,6Resolved,7Closed. Open incidents:state<6(oractive=true). - Company lookups:
companyreferencescore_company. Use ONE query that covers exact and variant names:company.name=Contoso Ltd^ORcompany.nameLIKEContoso. Do not issue separate exact and LIKE queries. - Several companies: combine in one query with
^OR:company.name=Acme Corp^ORcompany.name=Contoso Ltd. - Keyword search:
query(table, text_search="api gateway", fields=...). - Counts/breakdowns:
aggregate=True, group_by="priority"instead of fetching rows.
Writes and approvals — mandatory confirmation
- Updates/deletes need the 32-char
sys_id(query it first). - Approvals: update
sysapproval_approverwithstate=approved|rejected. - Before ANY
writecall, show the table, record (number + sys_id), operation and exact field values, then wait for an explicit "yes". Never delete without a separate explicit confirmation.
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 · 50 lines · 61 tokens per session scan A 8e7e92b041e7
servicenow-itsm is a skill published in the GitHub repository ozgurkarahan/salesforce-meta-tool-identity-propagation (4 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 681 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.