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 debugging-mutationsgit 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/debugging-mutations)<a href="https://agentmods.dev/skills/serac-labs/serac/debugging-mutations"><img src="https://agentmods.dev/badge/skills/serac-labs/serac/debugging-mutations/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/debugging-mutations"><img src="https://agentmods.dev/badge/skills/serac-labs/serac/debugging-mutations.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.00041 | $0.01333 |
| Opus 5.5 | $0.00016 | $0.00533 |
| Sonnet 5.5 | $0.00008 | $0.00267 |
| Haiku 4.5 | $0.00004 | $0.00133 |
Grade A, and why
debugging-mutations 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging & Mutation Inspection
When you've executed a tool against a ServiceNow instance and need to verify what actually happened — or diagnose why something didn't — these tools answer "what really changed and why". Use them after the fact, never as a substitute for picking the right tool in the first place.
Available debugging tools
| Tool | Purpose |
|---|---|
snow_inspect_mutations |
Inspect record changes (INSERT/UPDATE/DELETE) since a timestamp via sys_audit |
snow_get_logs |
Query platform logs with a time filter. Pass log_table to switch source: syslog (default), syslog_app_scope (scoped-app log), syslog_transaction (HTTP transactions), sys_script_execution_history (background-script traces) |
snow_session_context |
Dump the authenticated user, roles, current update set, domain. Use before ACL-sensitive debugging — "is this failing because I lack a role?" |
snow_get_script_output |
Output of previously executed scripts |
snow_trace_execution |
Server-side script execution tracing |
snow_get_flow_execution_logs |
Flow Designer execution history |
snow_get_inbound_http_logs |
Inbound REST API call logs |
snow_get_outbound_http_logs |
Outbound REST API call logs |
snow_audit_trail_analysis |
Audit trail analysis with anomaly detection |
snow_manage_flow (with verify=true) |
Verify a Flow Designer mutation immediately after running it |
Self-debugging workflows
Table API / REST changes (captured by sys_audit)
- Note the current timestamp before the action — or use a relative window like
"30s" - Execute the tool you want to verify
- Call
snow_inspect_mutationswithsince=<timestamp>orsince="30s" - Review which records were INSERT/UPDATE/DELETE, which fields changed, old → new values
- Compare expected vs. actual and adjust the calling code
Flow Designer (NOT captured by sys_audit)
Flow Designer uses GraphQL mutations against sys_hub_* tables, which sys_audit does not record. Use the Flow Designer tool's own verification path instead:
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 · 95 lines · 41 tokens per session scan A 005323c6265c
debugging-mutations is a skill published in the GitHub repository serac-labs/serac (78 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 1,333 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-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-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-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.