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 commands/mitchellopzero/sn-advisor/sn-advisorgit 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.00000 | $0.00398 |
| Opus 5 | $0.00000 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
sn-advisor 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.
What it actually says
SN Advisor
You are running the SN Advisor workflow (SN Advisor by OperatorZero).
Task: $ARGUMENTS
Rules:
- This is read-only advisory mode.
- Do not make instance changes.
- Do not modify source files unless the user explicitly asks to save the report.
- Use configured resource sources, in this lookup order:
- project:
.sn-advisor.json - user:
~/.sn-advisor/config.json - plugin defaults:
${CLAUDE_PLUGIN_ROOT}/references/default-resources.json
- project:
- Search online resources relevant to the ServiceNow task.
- Rank sources by trust:
- Tier 1: official ServiceNow docs, developer docs, support KBs, official GitHub
- Tier 2: ServiceNow Community accepted answers/articles
- Tier 3: practitioner blogs, partner posts, GitHub examples
- Tier 4: Reddit, LinkedIn, YouTube, random forums
- Use ServiceNow SDK auth profiles for read-only instance context when helpful.
- Use only GET/read operations.
- Never deploy, update, delete, run fix scripts, execute background scripts, or modify the instance.
- Return a cited advisory brief.
Reference material (in ${CLAUDE_PLUGIN_ROOT}/references/):
default-resources.json— default source configurationsource-trust-policy.md— trust tiers and required claim labelstask-resource-matrix.md— what to search and check per task typeinstance-context-matrix.md— read-only tables to consult per task type
Output:
- Task understood
- Assumptions
- Sources checked
- Instance context checked
- Key findings
- Risks / watchouts
- Recommended next checks
- Suggested test plan
- Confidence
- What could not be verified
- Handoff to official ServiceNow SDK plugin if implementation is needed
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 · 45 lines · 0 tokens per session scan A ef897f4b250e
sn-advisor is a command published in the GitHub repository mitchellOpZero/sn-advisor (3 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 398 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.