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 csm-patternsgit 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/csm-patterns)<a href="https://agentmods.dev/skills/serac-labs/serac/csm-patterns"><img src="https://agentmods.dev/badge/skills/serac-labs/serac/csm-patterns/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/csm-patterns"><img src="https://agentmods.dev/badge/skills/serac-labs/serac/csm-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 373 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00039 | $0.02723 |
| Opus 5.5 | $0.00016 | $0.01089 |
| Sonnet 5.5 | $0.00008 | $0.00545 |
| Haiku 4.5 | $0.00004 | $0.00272 |
Grade A, and why
csm-patterns 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 — 415 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Service Management for ServiceNow
CSM enables organizations to deliver exceptional customer service through cases, accounts, and self-service.
CSM Architecture
Account (customer_account)
├── Contacts (customer_contact)
├── Contracts (ast_contract)
│ └── Entitlements (service_entitlement)
├── Assets (alm_asset)
└── Cases (sn_customerservice_case)
├── Case Tasks
└── Communications
Key Tables
| Table | Purpose |
|---|---|
customer_account |
Customer accounts |
customer_contact |
Account contacts |
sn_customerservice_case |
Customer cases |
service_entitlement |
Service entitlements |
ast_contract |
Service contracts |
Customer Accounts (ES5)
Create Customer Account
// Create customer account (ES5 ONLY!)
var account = new GlideRecord("customer_account")
account.initialize()
// Basic info
account.setValue("name", "Acme Corporation")
account.setValue("account_code", "ACME-001")
account.setValue("industry", "Technology")
// Contact info
account.setValue("phone", "+1-555-123-4567")
account.setValue("email", "[email protected]")
account.setValue("website", "https://www.acme.com")
// Address
account.setValue("street", "123 Main Street")
account.setValue("city", "San Francisco")
account.setValue("state", "CA")
account.setValue("zip", "94105")
account.setValue("country", "US")
// Account details
account.setValue("account_type", "customer") // customer, partner, vendor
account.setValue("tier", "gold") // bronze, silver, gold, platinum
// Assignment
account.setValue("account_manager", accountManagerSysId)
account.insert()
Create Contact
// Create contact for account (ES5 ONLY!)
var contact = new GlideRecord("customer_contact")
contact.initialize()
// Link to account
contact.setValue("account", accountSysId)
// Contact info
contact.setValue("name", "John Smith")
contact.setValue("email", "[email protected]")
contact.setValue("phone", "+1-555-123-4568")
contact.setValue("title", "IT Manager")
// Contact type
contact.setValue("type", "primary") // primary, billing, technical
contact.setValue("active", true)
// Create user for portal access
var user = createUserFromContact(contact)
contact.setValue("user", user)
contact.insert()
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 · 415 lines · 39 tokens per session scan A f30503cd015d
csm-patterns is a skill published in the GitHub repository serac-labs/serac (78 stars, last pushed 5d ago), licensed Apache-2.0. It adds 39 tokens to every session and 2,723 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-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-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-uib
Review a ServiceNow UI Builder (UIB) experience or workspace page — its page map, what a change would touch, data broker security and page weight. Use when asked to explain, audit or assess a UI Builder page, workspace or experience before changing it.