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 jschuller/mcp-server-servicenow --skill exploring-tablesgit clone --depth 1 https://github.com/jschuller/mcp-server-servicenowWrote 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/jschuller/mcp-server-servicenow/exploring-tables)<a href="https://agentmods.dev/skills/jschuller/mcp-server-servicenow/exploring-tables"><img src="https://agentmods.dev/badge/skills/jschuller/mcp-server-servicenow/exploring-tables/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/jschuller/mcp-server-servicenow/exploring-tables"><img src="https://agentmods.dev/badge/skills/jschuller/mcp-server-servicenow/exploring-tables.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.00071 | $0.00963 |
| Opus 5 | $0.00036 | $0.00481 |
| Sonnet 5 | $0.00014 | $0.00193 |
| Haiku 4.5 | $0.00007 | $0.00096 |
Grade A, and why
exploring-tables 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploring ServiceNow Tables
General-purpose table exploration — schema discovery, data profiling, and table comparison.
Workflows
1. Explore a Table
Get the full picture of any ServiceNow table.
Progress checklist (copy into your response):
- [ ] Get table schema
- [ ] Pull sample records
- [ ] Summarize field types, mandatory fields, reference fields
- Get the table schema (field definitions, types, mandatory flags):
get_table_schema(table_name="<table_name>") - Pull sample records to see real data:
list_records(table_name="<table_name>", limit=5) - Summarize:
- Total field count and types (string, integer, reference, boolean, etc.)
- Mandatory fields (the ones users must populate)
- Reference fields (links to other tables — these define relationships)
- Choice fields (fields with dropdown values)
2. Compare Tables
Side-by-side schema comparison between two related tables.
Progress checklist:
- [ ] Get schema for table A
- [ ] Get schema for table B
- [ ] Compare field overlap and differences
- Get schemas for both tables:
get_table_schema(table_name="<table_a>") get_table_schema(table_name="<table_b>") - Compare:
- Fields present in both (shared/inherited from a common parent)
- Fields unique to each table
- Differences in field types or mandatory flags
- Reference field targets
3. Find Tables
Discover tables matching a keyword by querying sys_db_object.
Progress checklist:
- [ ] Query sys_db_object for matching tables
- [ ] Get record counts for top matches
- [ ] Summarize results
- Search for tables by name or label:
list_records(table_name="sys_db_object", query="nameLIKE<keyword>", fields="name,label,super_class,sys_id", limit=20) - For top matches, get a sample record to confirm the table has data:
list_records(table_name="<matched_table>", limit=1) - Summarize: table name, label, parent class, whether it has data.
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 · 120 lines · 71 tokens per session scan A 9d532902633f
exploring-tables is a skill published in the GitHub repository jschuller/mcp-server-servicenow (17 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 963 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-30.
Other skills, from other repositories
redteam-sqli-detail-pack
Domain routing and boundary guidance for authorized SQL injection testing, including union-based, blind, error-based, stacked query, and second-order SQL injection variants. Use when a task belongs to the SQL injection domain and needs scope, evidence, pivot, or exit criteria.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.
data-governance
Use this skill when designing or reviewing data governance: schema ownership, PII handling, retention, lineage, access policy, and migration safety for WrongStack services and stores. Triggers: user says "data governance", "PII", "schema ownership", "retention policy", "data lineage", "migration safety".
clickhouse-architect
ClickHouse schema design and optimization. TRIGGERS - ClickHouse schema, compression codecs, MergeTree, ORDER BY tuning, partition key.
database-designer
Design, review, or migrate database schemas using workload requirements, data integrity, query plans, and operational constraints.