route-environments

route-environments is a skill for Claude Code from microsoft/power-platform-skills. It costs 52 tokens per session (661 once invoked), scanned A, original, MIT.

A tool for checking how Power Platform chooses an environment for new makers. An environment is a separate workspace for Power Platform apps and flows.

In plain words
What is it for?
Use it to inspect environment routing, list environments, and set the current environment when working with Power Platform.
Why use it?
It shows whether routing sends new makers to a developer environment and helps identify default, developer, sandbox, and Dataverse-linked environments.

Skill for Claude Code ✓ vendor

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; names the AskUserQuestion tool; mentions Claude Code.

Part of the power-automate plugin — 9 skills shipped together

Good fit Use it to inspect environment routing, list environments, and set the current environment when working with Power Platform.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/power-platform-skills/route-environments
About the project

microsoft/power-platform-skills is a plugin marketplace containing reusable skills, agents, and commands for developing with Microsoft Power Platform. Developers use it to build and deploy Power Pages sites, model-driven Power Apps, and related solutions through Claude Code or GitHub Copilot. The catalogue entries are the marketplace's included skills, agents, plugins, and other agent components.

microsoft/power-platform-skills · 1,067 stars · on GitHub · aka.ms

Install

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.

Any agent
npx skills add microsoft/power-platform-skills --skill route-environments
Clone the repo
git clone --depth 1 https://github.com/microsoft/power-platform-skills

Made for: Claude Code.

Or install power-automate, the plugin that ships this one along with the rest of its 9 skills.

Wrote 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.

agentmods badge for route-environments

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/power-platform-skills/route-environments/github.svg)](https://agentmods.dev/skills/microsoft/power-platform-skills/route-environments)
Your own site
<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/route-environments"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/route-environments/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.

agentmods 80×15 button for route-environments

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/route-environments"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/route-environments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 661 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 7
    Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.
    Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.00661
Opus 5.5 $0.00021 $0.00264
Sonnet 5.5 $0.00010 $0.00132
Haiku 4.5 $0.00005 $0.00066

Measured 1mo ago against content hash f359451d9451, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

route-environments 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 1mo 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.

plugins/power-automate/skills/route-environments/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Environment Routing Manager

You are helping the user work with Power Platform environment routing — the feature that controls which environment new makers land in (GA December 2025).

Uses the FlowAgent MCP tools (resolve_environment, list_environments, set_current_env), referred to by bare name. In Claude Code they appear as mcp__flowagent__<tool>; in Copilot CLI as flowagent-<tool>.

Step 1: Check Current State

Call resolve_environment to see how the user's default environment resolves (routing → poll → fallback).

Step 2: Determine Operation

Check Routing Status

Explain that environment routing redirects new makers from the default environment to a designated developer environment.

Key facts:

  • Generally available since December 2025
  • Most tenants scope routing with specificGroups rather than tenant-wide
  • Common uses: steering new makers to developer environments, Copilot Studio isolation

List Environments

Call list_environments (use the query param to filter by name).

Show environment types and help the user identify:

  • Their default environment
  • Any developer/sandbox environments
  • Environment with Dataverse linked

Resolve Default Environment

Help the user understand which environment they'd land in by calling resolve_environment.

Guidance

  • Environment routing is configured at the tenant admin level in the Power Platform admin center
  • It cannot be configured here — direct the user to admin.powerplatform.microsoft.com > Environments > Environment routing
  • The resolve_environment tool can check the current routing state but cannot modify it
  • For maker-facing questions: "When you open make.powerautomate.com, environment routing determines which environment you see first"

Decision Tree

User asks about environment routing?
├── "What is it?" → Explain: redirects new makers from default to dev env
├── "Is it enabled?" → resolve_environment to check
├── "How do I enable it?" → Direct to PPAC admin center
├── "Which environment am I in?" → list_environments + resolve_environment
└── "What environments exist?" → list_environments with details

Read the full file on GitHub · 66 lines

Changes

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.

  1. 1mo ago Changed f359451d9451
  2. 1mo ago First seen · 66 lines · 52 tokens per session scan A 373218d6fadf

Subscribe to this mod's changes

route-environments is a skill published in the GitHub repository microsoft/power-platform-skills (1,067 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 661 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

canvas-apps-ui-gen

Generates paste-ready Power Apps Canvas App YAML. Invoke when the user wants to replicate a UI mockup, improve an existing Canvas app screen, or build a new screen from a text description. Also invoke when the user asks to "improve", "redesign", or "generate YAML" for a Canvas app screen.

ToluVictor/canvas-apps-tools · 71 tokens

traction-eos

Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…

wondelai/skills · 147 tokens

predictable-revenue

Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM). Use when the user mentions "outbound sales", "Cold Calling 2.0", "cold email sequences", "sales pipeline", "SDR process", "sales development", "build an outbound sales team", or "fill my pipeline". Also trigger when setting up a B2B…

wondelai/skills · 152 tokens

work

Execute Elixir/Phoenix plan tasks with progress tracking. Use after /phx:plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.

oliver-kriska/claude-elixir-phoenix · 43 tokens

catchup

Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.

oliver-kriska/claude-elixir-phoenix · 48 tokens

plan

Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.

oliver-kriska/claude-elixir-phoenix · 42 tokens