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-poolsgit 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-pools)<a href="https://agentmods.dev/commands/sdebruyn/fabric-dw-mcp-cli/sql-pools"><img src="https://agentmods.dev/badge/commands/sdebruyn/fabric-dw-mcp-cli/sql-pools.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.02599 |
| Opus 5 | $0.00000 | $0.01300 |
| Sonnet 5 | $0.00000 | $0.00520 |
| Haiku 4.5 | $0.00000 | $0.00260 |
Grade A, and why
sql-pools 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 3d 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 — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQL Pools
Manage custom SQL Pools at the workspace level with sub-resource commands that mirror the Azure CLI style. Callers must hold the workspace admin role.
Targets: Workspace (not item-specific)
CLI
sql-pools create
Targets: Workspace (not item-specific)
Add a new SQL pool to a workspace.
Synopsis
fdw [-w WORKSPACE] sql-pools create [OPTIONS]
| Option | Description |
|---|---|
--name TEXT |
Pool name. (required) |
--max-percent INTEGER |
Max resource percentage (1–100). (required) |
--default / --no-default |
Mark as default pool. Default: --no-default. |
--optimize-for-reads / --no-optimize-for-reads |
Enable read optimisation. Default: --optimize-for-reads. |
--classifier-type TEXT |
Classifier type (e.g. Application Name). |
--classifier-value TEXT |
Classifier value. Repeat for multiple values. |
Example
fdw -w MyWorkspace sql-pools create \
--name ETL \
--max-percent 30 \
--no-optimize-for-reads \
--classifier-type "Application Name" \
--classifier-value "ETL" \
--classifier-value "Load"
sql-pools delete
Targets: Workspace (not item-specific)
Remove a SQL pool from a workspace. You will be asked to confirm unless --yes is passed.
Synopsis
fdw [-w WORKSPACE] sql-pools delete [OPTIONS]
| Option | Description |
|---|---|
--name TEXT |
Pool name to delete. (required) |
--yes |
Skip confirmation prompt. |
Example
fdw -w MyWorkspace --yes sql-pools delete --name ETL
sql-pools disable
Targets: Workspace (not item-specific)
Disable custom SQL Pools for a workspace without deleting pool definitions. Re-enabling with sql-pools enable restores the previously saved configuration.
Synopsis
fdw [-w WORKSPACE] sql-pools disable
Example
fdw -w MyWorkspace sql-pools disable
sql-pools enable
Targets: Workspace (not item-specific)
Enable custom SQL Pools for a workspace. Preserves the existing pool configuration.
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.
- 3d ago First seen · 371 lines · 0 tokens per session scan A 55af53d84f02
sql-pools is a command published in the GitHub repository sdebruyn/fabric-dw-mcp-cli (10 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,599 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.