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 transform-mapsgit 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/transform-maps)<a href="https://agentmods.dev/skills/serac-labs/serac/transform-maps"><img src="https://agentmods.dev/badge/skills/serac-labs/serac/transform-maps/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/transform-maps"><img src="https://agentmods.dev/badge/skills/serac-labs/serac/transform-maps.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.00049 | $0.03287 |
| Opus 5.5 | $0.00020 | $0.01315 |
| Sonnet 5.5 | $0.00010 | $0.00657 |
| Haiku 4.5 | $0.00005 | $0.00329 |
Grade A, and why
transform-maps 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 — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Transform Maps for ServiceNow
Transform Maps control how data from import sets is mapped and transformed into ServiceNow tables.
Import Architecture
Data Source (CSV, LDAP, JDBC, REST)
↓
Import Set Table (staging)
↓
Transform Map (mapping rules)
↓
Target Table (final destination)
Key Components
| Component | Table | Purpose |
|---|---|---|
| Data Source | sys_data_source | Connection configuration |
| Import Set Table | sys_db_object | Staging table |
| Import Set | sys_import_set | Import run record |
| Transform Map | sys_transform_map | Mapping definition |
| Field Map | sys_transform_entry | Field mappings |
Data Sources
CSV Data Source (ES5)
// Create CSV data source
var ds = new GlideRecord("sys_data_source")
ds.initialize()
ds.setValue("name", "Employee Import - CSV")
ds.setValue("type", "File")
ds.setValue("format", "CSV")
// File settings
ds.setValue("file_path", "/import/employees.csv")
ds.setValue("header_row", 1)
// CSV parsing
ds.setValue("csv_delimiter", ",")
ds.setValue("csv_quote", '"')
// Import set table
ds.setValue("import_set_table", "u_employee_import")
ds.insert()
JDBC Data Source (ES5)
// Create JDBC data source
var ds = new GlideRecord("sys_data_source")
ds.initialize()
ds.setValue("name", "HR System - JDBC")
ds.setValue("type", "JDBC")
// Connection
ds.setValue("connection_url", "jdbc:oracle:thin:@hrdb:1521:HRPROD")
ds.setValue("username", "hr_readonly")
ds.setValue("password", "encrypted_password")
// Query
ds.setValue("query", "SELECT emp_id, first_name, last_name, email, dept_code FROM employees WHERE active = 1")
// Import set table
ds.setValue("import_set_table", "u_hr_employee_import")
ds.insert()
REST Data Source (ES5)
// Create REST data source
var ds = new GlideRecord("sys_data_source")
ds.initialize()
ds.setValue("name", "External API - REST")
ds.setValue("type", "REST (IntegrationHub)")
// REST message
ds.setValue("rest_message", restMessageSysId)
ds.setValue("http_method", "GET")
// Response handling
ds.setValue("json_path", "$.data.employees[*]")
// Import set table
ds.setValue("import_set_table", "u_api_employee_import")
ds.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 · 475 lines · 49 tokens per session scan A d08495eb513c
transform-maps is a skill published in the GitHub repository serac-labs/serac (78 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 3,287 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-09-11.
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-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.
sn-upgrade
Review ServiceNow upgrade readiness — the upgrade history, the skipped records an upgrade left unresolved, base vs customer versions of one skip, and store apps with an update. Use after a family or patch upgrade, before planning one, or when asked which skipped records to revert, keep or merge.
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.