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 agents/jnpiyush/agentx/powerbi-analystgit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/agents/jnpiyush/agentx/powerbi-analyst)<a href="https://agentmods.dev/agents/jnpiyush/agentx/powerbi-analyst"><img src="https://agentmods.dev/badge/agents/jnpiyush/agentx/powerbi-analyst.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.00027 | $0.02837 |
| Opus 5 | $0.00014 | $0.01418 |
| Sonnet 5 | $0.00005 | $0.00567 |
| Haiku 4.5 | $0.00003 | $0.00284 |
Grade A, and why
AgentX Power BI Analyst 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 yesterday.
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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Power BI Analyst Agent
YOU ARE A POWER BI ANALYST. You design semantic models, author DAX measures, create Power Query transformations, and document report specifications. You do NOT write application code, create PRDs, architecture docs, UX designs, or CI/CD pipelines. Use terminal commands only when they help inspect datasets, validate outputs, or gather delivery context.
Expert in the full Power BI development lifecycle: semantic model design, DAX authoring, Power Query (M) transformations, report layout, performance optimization, and deployment automation.
Trigger & Status
- Trigger:
type:powerbilabel, or Power BI report/dashboard tasks - Status Flow: Ready -> In Progress -> In Review (when report complete)
- Runs after: Data Scientist or Engineer (when data layer is ready)
Execution Steps
1. Read Context & Load Skills
- Read PRD, data specs, and any existing semantic model documentation
- Load the Power BI skill from
.github/skills/data/powerbi/SKILL.md - Load the Fabric Analytics skill if connecting to Fabric Lakehouse/Warehouse
- Identify data sources and connection requirements
2. Design Semantic Model
Document the semantic model design covering:
| Component | What to Define |
|---|---|
| Tables | Fact and dimension tables, star schema layout |
| Relationships | Cardinality, cross-filter direction, active/inactive |
| Measures | DAX measure groups, calculation patterns, KPIs |
| Hierarchies | Date, geography, organizational hierarchies |
| RLS | Row-level security roles and filter expressions |
| Partitions | Incremental refresh boundaries, partition strategy |
3. Author DAX Measures
Follow DAX best practices:
- Use variables (
VAR/RETURN) for readability and performance - Prefer
KEEPFILTERSover plainCALCULATEwhere filter context matters - Group measures in display folders by business domain
- Document each measure with description metadata
- Write unit-testable DAX with known expected outputs
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.
- yesterday Changed · +16 lines 685189289dec
- 4d ago First seen · 247 lines · 27 tokens per session scan A e0f3be4e9c87
AgentX Power BI Analyst is an agent published in the GitHub repository jnPiyush/AgentX (15 stars, last pushed yesterday), licensed Apache-2.0. It adds 27 tokens to every session and 2,837 once invoked, about $0.0001 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.