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 Bilal140202/the-lord-of-the-skills --skill aatrey882__servicenow-agent-skillsgit clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-skillsWrote 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/bilal140202/the-lord-of-the-skills/aatrey882__servicenow-agent-skills)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/aatrey882__servicenow-agent-skills"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/aatrey882__servicenow-agent-skills/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/bilal140202/the-lord-of-the-skills/aatrey882__servicenow-agent-skills"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/aatrey882__servicenow-agent-skills.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.00999 |
| Opus 5 | $0.00030 | $0.00500 |
| Sonnet 5 | $0.00012 | $0.00200 |
| Haiku 4.5 | $0.00006 | $0.00100 |
Grade A, and why
sn-scripting 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 9d 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.
This is a copy
100% identical to sn-scripting — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ServiceNow Legacy Scripting
ServiceNow legacy scripting uses the GlideRecord API for server-side data access, Script Include classes for reusable server-side logic, Business Rules for server-side automation, and g_form/g_user/g_list for client-side form manipulation. All APIs are described in the reference files below.
References
Read these files when you need them — do not pre-load all references at session start. Paths are relative to the skill root (the directory containing this SKILL.md file).
| File | When to Read |
|---|---|
references/gliderecord.md |
Generating or reviewing GlideRecord queries, CRUD operations, or addQuery/getValue patterns |
references/server-side.md |
Generating Script Includes, Business Rules, or using GlideSystem (gs.*) logging |
references/client-side.md |
Generating Client Scripts using g_form, g_user, or g_list; or any client-side form manipulation |
references/gotchas.md |
Before generating or reviewing any ServiceNow script — check for hallucination traps |
Scripts
| Script | When to use |
|---|---|
scripts/validate-script.sh |
When validating a ServiceNow script file for common issues before deploying |
Examples
Use these as structural templates — only read the example that matches your target type, do not pre-load all examples:
| File | Demonstrates |
|---|---|
assets/examples/gliderecord-crud.js |
Complete GlideRecord CREATE, READ (single and multi), UPDATE, DELETE with correct getValue() usage |
assets/examples/script-include-class.js |
Script Include using Class.create() pattern with initialize(), utility methods, and type property |
assets/examples/client-script-gform.js |
Client Script onLoad/onChange handlers using g_form.getValue(), g_form.setMandatory(), g_user.hasRole() |
Hard Rules
- Never use GlideRecord when ServiceNow Fluent SDK is present.
If the workspace contains
now.config.json,.now.tsfiles, or imports from@servicenow/sdk/core, the developer is working in a Fluent SDK application. Stop and redirect: "I can see you're working in a Fluent SDK project. Use the sn-sdk-fluent skill to generate typed metadata definitions instead of GlideRecord scripts. GlideRecord is the legacy scripting API and does not work inside Fluent SDK.now.tsfiles."
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.
- 9d ago First seen · 81 lines · 61 tokens per session scan A 538a237078b4
sn-scripting is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 61 tokens to every session and 999 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sn-scripting, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
firebase
Use when building on Firebase — Firestore data modeling, Security Rules, Auth and custom claims, Cloud Functions, Storage, modular Web/Admin SDK imports — including symptoms like a database open to the internet, a query rejected by rules, or a doc stuck at 1 write/sec. NOT managed-Postgres BaaS with SQL and RLS (that…
software-baas-platforms
Chooses managed backend platforms such as Supabase, Convex, and Firebase. Use when comparing database, auth, realtime, and backend-service tradeoffs.
shard
Designing multi-tenant architectures with tenant isolation strategies, RLS, routing, and scale design for SaaS. Use when designing multi-tenant SaaS systems or tenant isolation.
hunt-auth-bypass
Hunting skill for auth bypass vulnerabilities. Built from 4 public bug bounty reports. Use when hunting auth bypass on any target.
hunt-graphql
Hunting skill for graphql vulnerabilities. Built from 3 public bug bounty reports. Use when hunting graphql on any target.