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 exasol/mcp-server --skill exasol-system-tablesgit clone --depth 1 https://github.com/exasol/mcp-serverWrote 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/exasol/mcp-server/exasol-system-tables)<a href="https://agentmods.dev/skills/exasol/mcp-server/exasol-system-tables"><img src="https://agentmods.dev/badge/skills/exasol/mcp-server/exasol-system-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/exasol/mcp-server/exasol-system-tables"><img src="https://agentmods.dev/badge/skills/exasol/mcp-server/exasol-system-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.00047 | $0.02452 |
| Opus 5 | $0.00023 | $0.01226 |
| Sonnet 5 | $0.00009 | $0.00490 |
| Haiku 4.5 | $0.00005 | $0.00245 |
Grade A, and why
exasol-system-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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exasol System and Statistics Tables
Visibility Prefixes
Exasol system tables come in three visibility levels:
| Prefix | Accessible to | Shows |
|---|---|---|
EXA_ALL_* |
All users | Objects the current user has privileges on |
EXA_DBA_* |
DBA users only | All objects in the database |
EXA_USER_* |
All users | Objects owned by the current user |
Most day-to-day queries use EXA_ALL_*. If you need a complete picture (e.g., for auditing or capacity planning), use EXA_DBA_* (requires DBA role).
Metadata Tables
Schemas and Objects
| Table | Contents |
|---|---|
EXA_ALL_SCHEMAS |
All accessible schemas with SCHEMA_NAME, SCHEMA_OWNER, SCHEMA_COMMENT |
EXA_ALL_TABLES |
Tables and views: TABLE_SCHEMA, TABLE_NAME, TABLE_TYPE (TABLE/VIEW), TABLE_ROW_COUNT, TABLE_COMMENT |
EXA_ALL_COLUMNS |
Columns: COLUMN_SCHEMA, COLUMN_TABLE, COLUMN_NAME, COLUMN_TYPE, COLUMN_ORDINAL_POSITION, COLUMN_DEFAULT, COLUMN_IS_NULLABLE, COLUMN_COMMENT |
EXA_ALL_VIEWS |
View definitions: VIEW_SCHEMA, VIEW_NAME, VIEW_TEXT (DDL of the view) |
EXA_ALL_CONSTRAINTS |
Primary keys, foreign keys, not-null: CONSTRAINT_SCHEMA, CONSTRAINT_TABLE, CONSTRAINT_NAME, CONSTRAINT_TYPE |
EXA_ALL_CONSTRAINT_COLUMNS |
Which columns belong to each constraint |
Storage
| Table | Contents |
|---|---|
EXA_ALL_OBJECT_SIZES |
Per-object storage metrics: OBJECT_SCHEMA, OBJECT_NAME, OBJECT_TYPE, RAW_OBJECT_SIZE (uncompressed bytes), MEM_OBJECT_SIZE (compressed in-memory bytes), RAW_INDICES_SIZE, MEM_INDICES_SIZE, LAST_COMMIT (timestamp of last write activity) |
EXA_ALL_OBJECT_SIZES is the primary source for table size and freshness information. Join it with EXA_ALL_TABLES on schema and name to combine row counts with storage metrics.
Indices
| Table | Contents |
|---|---|
EXA_DBA_INDICES |
Auto-managed indices (DBA only): INDEX_SCHEMA, INDEX_TABLE, INDEX_TYPE (e.g. ENUM_KEY, ENUM_GROUP), RAW_OBJECT_SIZE, MEM_OBJECT_SIZE, LAST_COMMIT |
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 · 222 lines · 47 tokens per session scan A 4c2c5b5af06f
exasol-system-tables is a skill published in the GitHub repository exasol/mcp-server (18 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,452 once invoked, about $0.0002 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
pg-vacuum-tuning
Monitors and tunes PostgreSQL vacuum operations including autovacuum configuration, vacuum progress tracking, wraparound prevention, and per-table vacuum strategy. Provides tuning recommendations for high-churn OLTP and large analytical tables.
pg-bloat-analysis
Detects and remediates table and index bloat in PostgreSQL using pgstattuple analysis. Identifies fragmentation, dead tuples, and wasted space with prioritized maintenance actions including VACUUM, REINDEX, and pgrepack recommendations.
pg-health-check
Performs comprehensive PostgreSQL database health assessments covering connections, cache performance, locks, replication, wait events, active queries, and configuration review. Produces a scored health report with prioritized recommendations.
pg-index-optimization
Performs comprehensive PostgreSQL index optimization including unused index cleanup, duplicate detection, missing index recommendations, and hypothetical index testing with HypoPG. Provides actionable CREATE/DROP INDEX statements with estimated impact.
pg-lock-diagnosis
Diagnoses PostgreSQL lock contention including blocking lock chains, deadlock patterns, idle-in-transaction problems, and wait event analysis. Guides the agent through identifying blockers, understanding lock types, and recommending transaction and configuration changes.
pg-performance-baseline
Generates a comprehensive PostgreSQL performance baseline report capturing health metrics, query workload patterns, table statistics, configuration settings, index utilization, and I/O patterns. Designed for before/after comparison when making changes.