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-advisor-routernpx skills add mitchellOpZero/sn-advisor --skill sn-advisor-routergit clone --depth 1 https://github.com/mitchellOpZero/sn-advisorWrote 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/mitchellopzero/sn-advisor/sn-advisor-router)<a href="https://agentmods.dev/skills/mitchellopzero/sn-advisor/sn-advisor-router"><img src="https://agentmods.dev/badge/skills/mitchellopzero/sn-advisor/sn-advisor-router.svg" alt="Measured on agentmods" 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 | $0.00075 | $0.00554 |
| Opus 5 | $0.00037 | $0.00277 |
| Sonnet 5 | $0.00015 | $0.00111 |
| Haiku 4.5 | $0.00007 | $0.00055 |
Grade A, and why
sn-advisor-router 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 5d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SN Advisor Router
This skill routes ServiceNow advisory work. It is intentionally narrow so it can coexist with the official ServiceNow SDK plugin.
Use this skill when
- The user explicitly invokes
/sn-advisor. - The user asks for ServiceNow research.
- The user asks for current docs/community/support signals.
- The user asks for best practices.
- The user asks what to look out for.
- The user asks for risk assessment.
- The user asks for upgrade readiness.
- The user asks for troubleshooting context before action.
Do not use this skill when
- The user asks to create, edit, build, deploy, or implement ServiceNow code.
- The user asks to write Fluent SDK artifacts.
- The user asks to transform or deploy an app.
- The user asks for direct source changes.
For implementation, defer to the official ServiceNow SDK plugin.
Workflow
- Restate the task.
- Classify the ServiceNow domain:
- platform upgrade / release readiness
- UX / Next Experience / UI15 / UI16 / Workspace / UI Builder
- Service Portal / Employee Center
- ITSM process
- catalog / request / variables
- Flow Designer / workflow / approvals
- ACL / role / group / security
- CMDB / Discovery / Service Mapping
- integration / MID Server
- data import / transform maps
- notifications / events
- SLAs / schedules
- knowledge
- reporting / PA
- performance / technical debt
- Instance Scan / HealthScan-style review
- SDK/source-code task
- debugging / troubleshooting
- Load configured source policy.
- Search relevant online resources.
- Rank sources by trust.
- Pull read-only instance context through ServiceNow SDK auth profiles when useful.
- Produce the advisory brief.
- State explicitly that no changes were made.
- If implementation is requested next, hand off to the official ServiceNow SDK plugin.
Output contract
Return:
- Task understood
- Assumptions
- Sources checked
- Instance context checked
- Key findings
- Risks / watchouts
- Recommended next checks
- Suggested test plan
- Confidence
- What could not be verified
- Implementation handoff
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.
- 5d ago First seen · 75 lines · 75 tokens per session scan A 56e2da5c1de0
sn-advisor-router is a skill published in the GitHub repository mitchellOpZero/sn-advisor (3 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 554 once invoked, about $0.0004 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…