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/sdebruyn/fabric-dw-mcp-cli/sql-endpointsgit clone --depth 1 https://github.com/sdebruyn/fabric-dw-mcp-cliWrote 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/commands/sdebruyn/fabric-dw-mcp-cli/sql-endpoints)<a href="https://agentmods.dev/commands/sdebruyn/fabric-dw-mcp-cli/sql-endpoints"><img src="https://agentmods.dev/badge/commands/sdebruyn/fabric-dw-mcp-cli/sql-endpoints.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.00000 | $0.01190 |
| Opus 5 | $0.00000 | $0.00595 |
| Sonnet 5 | $0.00000 | $0.00238 |
| Haiku 4.5 | $0.00000 | $0.00119 |
Grade A, and why
sql-endpoints 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 today.
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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQL Analytics Endpoints
Manage Microsoft Fabric SQL Analytics Endpoints.
Targets: SQL Analytics Endpoint
Per-table freshness and refresh live in the tables group: see tables sync-status and tables refresh.
CLI
sql-endpoints get
Targets: SQL Analytics Endpoint
Get details for a specific SQL Analytics Endpoint.
Synopsis
fdw [-w WORKSPACE] sql-endpoints get ENDPOINT
Example
fdw -w MyWorkspace sql-endpoints get MyLakehouseEP
sql-endpoints list
Targets: SQL Analytics Endpoint
List all SQL Analytics Endpoints in a workspace. Supports -A / --all-workspaces to scan every visible workspace. -w / --workspace and --all-workspaces are mutually exclusive.
Synopsis
fdw [-w WORKSPACE] sql-endpoints list [-A]
| Option | Description |
|---|---|
-A / --all-workspaces |
Scan all visible workspaces and aggregate results. Mutually exclusive with -w. |
Example
# List endpoints in the default (or configured) workspace
fdw sql-endpoints list
# List endpoints in a specific workspace
fdw -w MyWorkspace sql-endpoints list
# Aggregate across all visible workspaces
fdw sql-endpoints list --all-workspaces
displayName id
------------------ ------------------------------------
MyLakehouseEP f9e1...
sql-endpoints refresh
Targets: SQL Analytics Endpoint
Refresh metadata for a SQL Analytics Endpoint by triggering a sync from the underlying Lakehouse delta tables. This is a long-running operation (LRO) that is polled to completion.
Results are shown as a Rich table (Table, Status, End Time, Error). Pass --json on the root command to emit raw JSON instead.
Synopsis
fdw [-w WORKSPACE] sql-endpoints refresh [--recreate-tables] ENDPOINT
Options
| Flag | Description |
|---|---|
--recreate-tables |
Drop and recreate all tables during the refresh. Use to resolve inconsistencies or force a clean rebuild. Destructive: use with caution. |
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.
- today Changed · +14 lines 90fa49a53db1
- 4d ago First seen · 140 lines · 0 tokens per session scan A 8a2432f24ec8
sql-endpoints is a command published in the GitHub repository sdebruyn/fabric-dw-mcp-cli (10 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,190 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
check_schema_version
Check the Flyway schema version of the SQLite database on a Docker volume.
skene-status
Check implementation status from skene-context/engine.yaml. Validates features, action vs code-only mode, and that trigger/function SQL exists in migrations; detail shows latest matching file and (+N) if duplicates.
sql_schema
Command "sql_schema" from agentis-tools/ctx, covering ctx sql — public schema (v1), stability contract, views, v1.symbols — one row per symbol and v1.edges — one row per relationship.
sql
Run read-only SQL against the code-intelligence index through DuckDB, over a stable v1 view layer.
reflect
Reflect on an outcome to update memory confidence and create relationships in the central Gnosys database.
restore
Restore the central Gnosys database from a backup file.