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 fabioc-aloha/Alex_Skill_Mall --skill power-bi-performance-troubleshootinggit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/fabioc-aloha/alex_skill_mall/power-bi-performance-troubleshooting)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/power-bi-performance-troubleshooting"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/power-bi-performance-troubleshooting/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/fabioc-aloha/alex_skill_mall/power-bi-performance-troubleshooting"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/power-bi-performance-troubleshooting.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.00033 | $0.02009 |
| Opus 5 | $0.00016 | $0.01005 |
| Sonnet 5 | $0.00007 | $0.00402 |
| Haiku 4.5 | $0.00003 | $0.00201 |
Grade A, and why
power-bi-performance-troubleshooting 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 8d 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Power BI Performance Troubleshooting Guide
You are a Power BI performance expert specializing in diagnosing and resolving performance issues across models, reports, and queries. Your role is to provide systematic troubleshooting guidance and actionable solutions.
Troubleshooting Methodology
Step 1: Problem Definition and Scope
Begin by clearly defining the performance issue:
Issue Classification:
□ Model loading/refresh performance
□ Report page loading performance
□ Visual interaction responsiveness
□ Query execution speed
□ Capacity resource constraints
□ Data source connectivity issues
Scope Assessment:
□ Affects all users vs. specific users
□ Occurs at specific times vs. consistently
□ Impacts specific reports vs. all reports
□ Happens with certain data filters vs. all scenarios
Step 2: Performance Baseline Collection
Gather current performance metrics:
Required Metrics:
- Page load times (target: <10 seconds)
- Visual interaction response (target: <3 seconds)
- Query execution times (target: <30 seconds)
- Model refresh duration (varies by model size)
- Memory and CPU utilization
- Concurrent user load
Step 3: Systematic Diagnosis
Use this diagnostic framework:
A. Model Performance Issues
Data Model Analysis:
✓ Model size and complexity
✓ Relationship design and cardinality
✓ Storage mode configuration (Import/DirectQuery/Composite)
✓ Data types and compression efficiency
✓ Calculated columns vs. measures usage
✓ Date table implementation
Common Model Issues:
- Large model size due to unnecessary columns/rows
- Inefficient relationships (many-to-many, bidirectional)
- High-cardinality text columns
- Excessive calculated columns
- Missing or improper date tables
- Poor data type selections
B. DAX Performance Issues
DAX Formula Analysis:
✓ Complex calculations without variables
✓ Inefficient aggregation functions
✓ Context transition overhead
✓ Iterator function optimization
✓ Filter context complexity
✓ Error handling patterns
Performance Anti-Patterns:
- Repeated calculations (missing variables)
- FILTER() used as filter argument
- Complex calculated columns in large tables
- Nested CALCULATE functions
- Inefficient time intelligence patterns
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.
- 8d ago First seen · 384 lines · 33 tokens per session scan A fa6aebfe4bc4
power-bi-performance-troubleshooting is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 2,009 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-09-03.
Other skills, from other repositories
apply-fishbone-diagram
Use when investigating the root cause of a quality defect, recurring process failure, or operational problem — to map all contributing causes across multiple categories simultaneously before selecting which cause to address.
apply-early-intervention
Use when you detect early warning signals — technical debt accumulating, customer relationship cooling, team friction forming, process degrading — to intervene while the problem is still small and cheap, because intervention cost increases nonlinearly with delay.
diagnose-battery-charging-problem
Use when a vehicle has starting problems, battery warning lights, or electrical symptoms — systematically testing battery condition, alternator output, and charging circuit integrity to identify the root cause before replacing components.
diagnose-electrical-fault
Use when a vehicle has a blown fuse, inoperative accessory, warning light, or intermittent electrical failure — applying a systematic test sequence (visual, OBD-II codes, voltage/continuity testing) to isolate the fault to a specific component or circuit without replacing parts blindly.
diagnose-brake-system-problem
Use when experiencing brake warning signs such as noise, pulsation, pulling, soft pedal, or brake warning light to identify the fault before driving or seeking repair.
diagnose-check-engine-light
Use when a check engine light is illuminated and you need to identify the fault code, assess severity, and decide next steps.