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 santoshkanthety/powerbi-agent --skill powerbi-tmdlgit clone --depth 1 https://github.com/santoshkanthety/powerbi-agentWrote 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/santoshkanthety/powerbi-agent/powerbi-tmdl)<a href="https://agentmods.dev/skills/santoshkanthety/powerbi-agent/powerbi-tmdl"><img src="https://agentmods.dev/badge/skills/santoshkanthety/powerbi-agent/powerbi-tmdl/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/santoshkanthety/powerbi-agent/powerbi-tmdl"><img src="https://agentmods.dev/badge/skills/santoshkanthety/powerbi-agent/powerbi-tmdl.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00110 | $0.05658 |
| Opus 5 | $0.00055 | $0.02829 |
| Sonnet 5 | $0.00022 | $0.01132 |
| Haiku 4.5 | $0.00011 | $0.00566 |
Grade A, and why
powerbi-tmdl 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 12d 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 — 488 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TMDL Authoring
Expert guidance for authoring and editing TMDL (Tabular Model Definition Language) files directly in PBIP projects.
This skill is a last resort. Direct TMDL file editing lacks the validation, atomicity, and DAX query capabilities of the Tabular Editor CLI, Power BI MCP server, or the
connect-pbidskill (TOM via PowerShell). Use those tools when available. TMDL editing is appropriate when:
- Working with PBIP files in a Git repo without Power BI Desktop open
- No Tabular Editor CLI or MCP server is installed
- Making quick text-level fixes (descriptions, format strings, display folders) where a full tool chain is overkill
Direct TMDL editing does not validate DAX syntax, check referential integrity, or verify that property values are valid. Errors will only surface when the model is next loaded in Power BI Desktop or deployed via XMLA. Use the
pbip-validatoragent to check TMDL files for syntax issues, indentation errors, and referential integrity before opening in PBI Desktop.
Validation: tmdl-validate v0.2.0
tmdl-validate supports two modes:
# Single-file mode — validate one .tmdl file (used by PostToolUse hook per edit)
tmdl-validate path/to/tables/Sales.tmdl
# Directory mode — validate the whole model at once (v0.2.0+)
tmdl-validate path/to/Model.SemanticModel/definition
Directory mode adds one critical check not in single-file mode:
M-expression name collision — expressions.tmdl defines named shared expressions (Power Query parameters and queries). If a shared expression has the same name as a table, the model fails to load in Desktop with a silent error. Directory mode detects this.
# Example collision — expression "Sales" collides with table "Sales"
# expressions.tmdl:
expression Sales = ... # ← same name as a table in tables/Sales.tmdl
Fix: rename the shared expression or the table so names are unique across both expressions.tmdl and tables/.
When to use directory mode:
- After bulk renames (tables, shared expressions, parameters)
- After adding new tables or M parameters
- Before any Desktop open or XMLA deploy
- When
pbip-validatorreports unexplained load failures
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.
- 12d ago First seen · 488 lines · 110 tokens per session scan A 2ff3e15fdaba
powerbi-tmdl is a skill published in the GitHub repository santoshkanthety/powerbi-agent (2 stars, last pushed 13d ago), licensed MIT. It adds 110 tokens to every session and 5,658 once invoked, about $0.0006 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-31.
Other skills, from other repositories
seshat-bi
Route a BI project through Seshat BI's governed seven-stage readiness flow. Use when a user asks to inspect a retail source, initialize a Seshat project, find the truthful next action, validate readiness evidence, or stop at the correct human approval gate.
Data Retention Schedule Review
Use when reviewing a draft or existing data retention schedule to inventory data categories against stated purposes, collect retention-period facts, flag legal-hold interactions, and surface orphaned-data and vendor-coverage gaps for attorney review.
powerbi-workflows
Route guarded Power BI work -- design, native report authoring, semantic-model operations, published queries, QA, bounded formatting, and PBIP adoption -- to the correct Seshat or official Microsoft surface under Seshat BI's gates.
dbt-workflows
Route dbt intent to Seshat's governed shadow workflow or the official dbt Labs competence and execution owner, without bypassing readiness or evidence.
dagster-workflows
Route Dagster intent to Seshat's governed medallion workflow or the official Dagster competence owner without bypassing readiness, approvals, or evidence.
pbi-mcp-doctor
Use when a user asks whether or how to wire Microsoft's official Power BI MCP servers into a Seshat BI workspace: run the read-only environment doctor, map a task to the governed Power BI surface (including the official report-authoring skill), generate a safe read-only config template, or run the mocked read-only…