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 agentmods add skills/mitchellopzero/sn-advisor/sn-instance-readonlynpx skills add mitchellOpZero/sn-advisor --skill sn-instance-readonlygit clone --depth 1 https://github.com/mitchellOpZero/sn-advisorWhat 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 | $0.00023 | $0.00491 |
| Opus 5 | $0.00012 | $0.00246 |
| Sonnet 5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
sn-instance-readonly 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 2d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ServiceNow Instance Read-Only Context
Use this skill when advisor output would be materially improved by checking live instance context.
Access model
Use ServiceNow SDK auth profiles only.
Expected profile discovery:
npx @servicenow/sdk auth --list
Use the configured default alias if present. Otherwise ask the user which alias to use. The selected profile's ServiceNow ACLs are the access boundary.
Hard guardrails
- GET/read only.
- No POST, PUT, PATCH, DELETE.
- No deploy.
- No build/publish side effects.
- No fix scripts.
- No background scripts.
- ServiceNow ACLs and the selected SDK auth profile determine what can be read.
- Any table and any readable field may be queried when useful for the task.
- Do not maintain an advisor-owned table denylist by default.
- Do not redact field values by default; trust ServiceNow ACLs and the selected profile.
- Respect max record limits.
Useful context by task
Upgrade:
- instance version/build
- active plugins
- upgrade history
- skipped updates
- relevant system properties
- modified OOB records where safely visible
UX:
- UI-related system properties
- user preferences for UI15/UI16/Next Experience
- active themes/branding
- homepages/dashboards
- workspaces
- portals
- UI scripts, UI macros, UI pages
- client scripts and UI policies
ITSM/table process:
- table dictionary
- business rules
- client scripts
- UI policies
- ACLs
- assignment rules
- flows/workflows
- notifications
- SLAs
Catalog:
- catalog item
- variables and variable sets
- catalog client scripts
- catalog UI policies
- flows/workflows
- approvals
- portals where exposed
Security:
- ACLs
- roles/groups metadata
- table hierarchy
- before-query business rules
- user criteria
Integrations:
- REST messages metadata
- scripted REST APIs
- MID Server status/config
- scheduled imports
- transform maps
Output language
Always state:
"Read-only instance context checked. No instance changes were made."
If instance access is unavailable, state what could not be verified and continue using online sources.
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.
- 2d ago First seen · 97 lines · 23 tokens per session scan A 29d647319c84
sn-instance-readonly is a skill published in the GitHub repository mitchellOpZero/sn-advisor (3 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 491 once invoked, about $0.0001 per session on Opus 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.