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 orchestra-hq/orchestra-skills --skill powerbi-dagster-to-orchestragit clone --depth 1 https://github.com/orchestra-hq/orchestra-skillsWrote 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/orchestra-hq/orchestra-skills/powerbi-dagster-to-orchestra)<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/powerbi-dagster-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/powerbi-dagster-to-orchestra/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/orchestra-hq/orchestra-skills/powerbi-dagster-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/powerbi-dagster-to-orchestra.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.00139 | $0.03319 |
| Opus 5 | $0.00069 | $0.01659 |
| Sonnet 5 | $0.00028 | $0.00664 |
| Haiku 4.5 | $0.00014 | $0.00332 |
Grade A, and why
powerbi-dagster-to-orchestra 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Power BI: Dagster -> Orchestra Conversion
Overview
Dagster has an official dagster-powerbi integration for semantic model (dataset) refreshes: a PowerBIWorkspace (configured with PowerBIServicePrincipal or PowerBIToken credentials plus a workspace_id) is used with load_powerbi_asset_specs to snapshot the workspace as asset specs, and build_semantic_model_refresh_asset_definition turns a semantic-model asset spec into a materializable asset that triggers a refresh (internally calling power_bi.trigger_and_poll_refresh(dataset_id)).
Critical: load_powerbi_asset_specs auto-discovers every dataset/dataflow/report/dashboard from the live Power BI workspace by calling the Power BI API when Dagster's definitions load. The actual dataset GUIDs are almost never written anywhere in the static Python source — they only exist as live data returned by that API call. Each discovered dataset's GUID is exposed as spec.metadata["dagster-powerbi/id"] at runtime, but that's a live value, not something you can read off the page. This means: don't expect to find a real dataset GUID sitting in the source code. Only trust a literal you can actually see (a hardcoded GUID, or one read from an env var/Variable with a visible default). If the code just loops over all discovered specs with no such visible value, the real GUID genuinely isn't determinable from source — see Conversion Steps and Gotchas for what to do instead of guessing.
dagster-powerbi has no documented support for dataflow refresh — if a Dagster codebase refreshes a Power BI dataflow, it is almost always a hand-rolled @op or custom ConfigurableResource that calls the Power BI REST API directly (POST /groups/{groupId}/dataflows/{dataflowId}/refreshes) and polls the transaction status. Treat that pattern the same way you'd treat any custom REST-wrapping resource — there's no dedicated Dagster class to look for.
In Orchestra, both cases map to the POWER_BI integration.
Parameter Mapping
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 · 185 lines · 139 tokens per session scan A 2ef237fd8ac7
powerbi-dagster-to-orchestra is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed 3d ago), licensed MIT. It adds 139 tokens to every session and 3,319 once invoked, about $0.0007 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…