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-airflow-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-airflow-to-orchestra)<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/powerbi-airflow-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/powerbi-airflow-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-airflow-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/powerbi-airflow-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.00125 | $0.02706 |
| Opus 5 | $0.00063 | $0.01353 |
| Sonnet 5 | $0.00025 | $0.00541 |
| Haiku 4.5 | $0.00013 | $0.00271 |
Grade A, and why
powerbi-airflow-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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Power BI: Airflow → Orchestra Conversion
Overview
Airflow's PowerBIDatasetRefreshOperator (from airflow.providers.microsoft.azure.operators.powerbi) triggers a Power BI dataset (semantic model) refresh via an Azure service-principal connection and — being deferrable — waits for the refresh to complete using the Power BI REST API. In Orchestra the equivalent is a task under the POWER_BI integration.
There is no dedicated Airflow operator for dataflow refreshes in apache-airflow-providers-microsoft-azure as of this writing. A dataflow refresh in an Airflow DAG is typically hand-rolled as a PythonOperator/HttpOperator call against the Power BI REST API (POST /groups/{groupId}/dataflows/{dataflowId}/refreshes). Do not invent an operator name for this — treat any such hand-rolled task as a candidate for POWER_BI_REFRESH_DATAFLOW based on what the code is actually calling.
Parameter Mapping
| Airflow parameter | Orchestra YAML field | Notes |
|---|---|---|
conn_id (e.g. powerbi_default) |
connection: |
Orchestra Power BI connection (Azure service principal) |
dataset_id |
parameters.dataset_id |
Required for POWER_BI_REFRESH_DATASET |
group_id |
parameters.workspace_id |
Airflow's group_id is Orchestra's workspace_id — same Power BI workspace GUID, renamed field. Leave null unless this task's workspace differs from the one configured on the Orchestra connection — see Gotchas |
(hand-rolled dataflow call) dataflowId |
parameters.dataflow_id |
Required for POWER_BI_REFRESH_DATAFLOW instead of dataset_id |
| n/a (Airflow has no equivalent knob) | parameters.refresh_type |
Optional — one of Full, ClearValues, Calculate, DataOnly, Automatic, Defragment (mirrors Power BI's own DatasetRefreshType enum). Leave null/omit unless the DAG explicitly requests a non-default refresh type. |
| n/a | parameters.apply_refresh_policy |
Optional boolean, defaults to null. Only set if the source DAG's REST call explicitly passes applyRefreshPolicy. |
task_id |
name: |
Human-readable task name |
upstream >> chains |
depends_on: |
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 · 192 lines · 125 tokens per session scan A 5b29a46ea460
powerbi-airflow-to-orchestra is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed 3d ago), licensed MIT. It adds 125 tokens to every session and 2,706 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
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…