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 tmdl-linter-false-positivesgit 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/tmdl-linter-false-positives)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/tmdl-linter-false-positives"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/tmdl-linter-false-positives/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/tmdl-linter-false-positives"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/tmdl-linter-false-positives.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.00031 | $0.00490 |
| Opus 5 | $0.00015 | $0.00245 |
| Sonnet 5 | $0.00006 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
tmdl-linter-false-positives 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 9d 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.
What it actually says
TMDL Linter False Positives
The Problem
VS Code's TMDL (Tabular Model Definition Language) linter reports valid syntax as errors:
measure 'Total Sales' = SUM('Sales'[Amount])
description = "Sum of all sales amounts" // Linter: "Invalid property 'description'"
The description property IS valid — this is a linter limitation.
The Solution
Ignore these specific false positives:
Known False Positives
| Property | Context | Actual Status |
|---|---|---|
description |
On measures | ✅ Valid |
description |
On columns | ✅ Valid |
formatString |
Some contexts | ✅ Valid |
displayFolder |
On measures | ✅ Valid |
Verification
Test in Power BI Desktop or Tabular Editor:
- Apply the TMDL
- If it loads without error, the syntax is correct
- The VS Code linter is wrong, not your code
Workaround Options
Option 1: Ignore the Squiggles
The TMDL will work — the linter is just incomplete.
Option 2: Suppress in Settings
// .vscode/settings.json
{
"tmdl.validate": false
}
Option 3: Use Tabular Editor
Tabular Editor's TMDL support is more complete.
When Linter IS Correct
| Error | Likely Real |
|---|---|
Syntax errors (missing =, unmatched quotes) |
Yes |
| Unknown table/column references | Yes |
| DAX function errors | Yes |
| Property on wrong object type | Maybe |
Verification
# Deploy to test
# If no error in Power BI/SSAS, linter was wrong
When to Apply
- TMDL development in VS Code
- Any unexpected linter error on common properties
- When syntax looks correct but shows errors
Tags
data tmdl power-bi linting false-positive
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.
- 9d ago First seen · 85 lines · 31 tokens per session scan A f9f9abc6837e
tmdl-linter-false-positives is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 490 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.