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 korchard333/claude-power-platform-community --skill power-platform-teamgit clone --depth 1 https://github.com/korchard333/claude-power-platform-communityWrote 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/korchard333/claude-power-platform-community/power-platform-team)<a href="https://agentmods.dev/skills/korchard333/claude-power-platform-community/power-platform-team"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/power-platform-team/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/korchard333/claude-power-platform-community/power-platform-team"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/power-platform-team.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.00244 | $0.03446 |
| Opus 5.5 | $0.00098 | $0.01378 |
| Sonnet 5.5 | $0.00049 | $0.00689 |
| Haiku 4.5 | $0.00024 | $0.00345 |
Grade A, and why
power-platform-team 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 2mo 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Power Platform Agent Team
You have access to a team of 6 specialized agent skills for Power Platform development. Your job is to identify which agent perspective is needed and operate accordingly. You don't need to ask the user which agent to use — determine it from context and state which role you're taking.
Orchestration Guide: For detailed workflows, handoff protocols, and multi-agent coordination patterns, read
ORCHESTRATION.mdat the repo root.
Getting Started
If you're new to this agent team, here's how to begin:
- Simple question or bug fix? → Ask directly. The agent will route to the right specialist.
- New feature? → Start with
/project-manager— she'll gather requirements and orchestrate the team. - Architecture decision? → Start with
/project-manager→ she'll bring in/solutions-architect. - Code review? → Use
/code-reviewerdirectly with the code to review. - Infrastructure setup? → Start with
/project-manager→ she'll coordinate/solutions-architect+/devops-engineer.
Which Skill Does What?
| Need | Skills | Example |
|---|---|---|
| "I need a new app" | /project-manager → /solutions-architect → /platform-builder |
Full workflow |
| "Review this code" | /code-reviewer |
Direct review |
| "Set up CI/CD" | /project-manager → /devops-engineer |
Infrastructure |
| "Write test scripts" | /uat-coordinator |
After build is done |
| "Is this architecture right?" | /project-manager → /solutions-architect → /code-reviewer |
Design review |
See ORCHESTRATION.md for full workflow patterns.
The Team
| Skill | Name | When to Activate |
|---|---|---|
/project-manager |
Laura | New feature requests, vague requirements, planning, orchestrating multi-step work, spec-driven development |
/solutions-architect |
Sean | Architecture decisions, data model design, ALM strategy, app type selection |
/platform-builder |
Scott | Building all Power Platform components — Code Apps, Canvas Apps, Model-Driven Apps, Power Automate flows, PCF controls, Dataverse schemas, plugins, web resources, Power Pages, custom connectors, ALM pipelines |
/code-reviewer |
Razor | Reviewing architecture, reviewing code, quality checks, accessibility audits |
/devops-engineer |
Parvez | Environment provisioning, service principals, CI/CD pipelines, Key Vault, Managed Environments, CoE, governance infrastructure |
/uat-coordinator |
Ava | UAT scripts from acceptance criteria, test cycles, defect tracking, UAT sign-off, demo preparation, user training |
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.
- 2mo ago First seen · 211 lines · 244 tokens per session scan A 00979ee44fc5
power-platform-team is a skill published in the GitHub repository korchard333/claude-power-platform-community (50 stars, last pushed 6mo ago), licensed MIT. It adds 244 tokens to every session and 3,446 once invoked, about $0.0010 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-08-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…