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 serac-labs/serac --skill csdm-modelinggit clone --depth 1 https://github.com/serac-labs/seracWrote 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/serac-labs/serac/csdm-modeling)<a href="https://agentmods.dev/skills/serac-labs/serac/csdm-modeling"><img src="https://agentmods.dev/badge/skills/serac-labs/serac/csdm-modeling/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/serac-labs/serac/csdm-modeling"><img src="https://agentmods.dev/badge/skills/serac-labs/serac/csdm-modeling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.04698 |
| Opus 5.5 | $0.00021 | $0.01879 |
| Sonnet 5.5 | $0.00011 | $0.00940 |
| Haiku 4.5 | $0.00005 | $0.00470 |
Grade A, and why
csdm-modeling 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 1mo ago.
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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CSDM Modeling
The Common Service Data Model is ServiceNow's prescription for which table a service record goes in.
It is not a plugin, not a field, and not something you switch on. It is a set of classes that already
exist in your CMDB, plus guidance about which one a given record belongs to. Get the class wrong and
nothing fails today — the record saves, the tool returns created: true, and the bill arrives later.
ServiceNow's own migration guidance is blunt about the trade: you can keep using non-conforming tables,
but "you might not get the full benefit of your products", and moving CIs to the right table afterwards
does not move the reports, business rules and references already pointing at them, while "during
migration, you lose all customized or base-system attributes that are not in the same table hierarchy".
This guide is about the model. cmdb-patterns is about the tools — relationship mechanics, orphan and
stale detection, the cmdb_rel_type lookup. Read that one for those.
The default mistake
Asked to "create a business service", an agent reaches for snow_create_ci with
ci_class: "cmdb_ci_service". That produces a record in the base Service class — precisely the record
ServiceNow publishes a migration path off of. A dedicated Business Service class exists, the guidance
to move records into it is published, and a large share of long-lived instances are carrying exactly
that backlog right now.
Never create a record in cmdb_ci_service. It is a parent class. Records belong in one of its
children.
The classes, and what belongs in each
| What you are modelling | Table | Platform label |
|---|---|---|
| A service published to business users | cmdb_ci_service_business |
Business Service |
| A service published to service owners, underpinning business services | cmdb_ci_service_technical |
Technology Management Service (formerly Technical Service) |
| A specific consumable variant of a service, with commitments | service_offering |
Service Offering |
| A running, mapped instance of an application and its infrastructure | cmdb_ci_service_auto |
Service Instance (formerly Application Service) |
| The same, created by the Manual service population method | cmdb_ci_service_discovered |
Mapped Application Service |
| The conceptual application the business talks about | cmdb_ci_business_app |
Business Application |
| The installed software instance on a host | cmdb_ci_appl |
Application |
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.
- 1mo ago First seen · 328 lines · 53 tokens per session scan A 8346f1525a32
csdm-modeling is a skill published in the GitHub repository serac-labs/serac (78 stars, last pushed 8d ago), licensed Apache-2.0. It adds 53 tokens to every session and 4,698 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-08-30.
Other skills, from other repositories
sn-safe-write
Change ServiceNow data safely — plan first, apply only after review, verify, and know how to revert. Use whenever a create, update, upsert or delete on an instance is requested.
sn-discover
Map a ServiceNow instance into Markdown (version and counts, custom applications, per-scope tables and artefacts) with the server's own document generator. Use when asked to discover, survey, inventory or document an instance or its custom apps.
sn-drift
Find configuration drift between two ServiceNow instances or against a saved snapshot, or review what an update set will change. Use when comparing dev / test / prod, checking a promotion, or reviewing an update set.
sn-impact
Estimate the blast radius of changing a ServiceNow table, field or script — what references it and what automation runs around it. Use before renaming, deleting or changing a field, table, script include or business rule.
sn-triage
Triage a ServiceNow incident or a failing behaviour — instance health, recent errors, what automation runs on the table, and what changed on the record. Use when something is broken, slow or erroring on an instance.
sn-security
Review the security posture of a ServiceNow instance — the ACL scan, hardening properties and cross-scope access — or explain why one user can or cannot read, write, create or delete a table, record or field. Use for a security review, a hardening check, or a "why can't this user see / edit it" question.