Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/korchard333/claude-power-platform-communitynpx agentmods add skills/korchard333/claude-power-platform-community/almWrote 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/alm)<a href="https://agentmods.dev/skills/korchard333/claude-power-platform-community/alm"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/alm/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/alm"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/alm.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.00046 | $0.04043 |
| Opus 5 | $0.00023 | $0.02021 |
| Sonnet 5 | $0.00009 | $0.00809 |
| Haiku 4.5 | $0.00005 | $0.00404 |
Grade A, and why
alm 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 10d 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 — 544 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Application Lifecycle Management (ALM)
When to Use
Trigger when designing deployment pipelines, managing solutions, promoting across environments, or setting up CI/CD for Power Platform.
ALM Golden Rules
- Never import unmanaged solutions to Test or Production
- Every environment needs a dedicated service principal — no human accounts in pipelines
- Environment variables must be set per environment — never hardcoded
- Connection references must be pre-created before solution import
- Solution version must increment on every build (major.minor.build.revision)
- Always run Solution Checker before promoting to Test/Prod
⚠️ REQUIRED: Load Sub-Files Before Implementation
SKILL.md is a summary only — it is NOT sufficient for implementation.
The detailed content (complete payloads, XML templates, working examples, edge-case handling) lives in sub-files in the same directory as this SKILL.md. Before writing any code, you MUST use read_file on the sub-files relevant to your task:
- Developer Inner Loop — Three development loops (Web API direct, pac code push, pac solution sync), when to use each, day-to-day workflows
- Git Integration — Native Git integration in maker portal, deploy from Git (2026 wave 1), branch strategies for Power Platform, Azure DevOps Boards integration
- Azure DevOps Pipelines — ADO pipeline YAML templates, service connections, multi-stage deployment, variable groups
Solution Lifecycle
Developer writes code / configures in Dev (unmanaged)
↓
Export solution from Dev → Unpack to source control
↓
CI pipeline: Pack → Solution Checker → Build managed artifact
↓
CD pipeline: Import managed solution to Test → Smoke test
↓
CD pipeline: Import managed solution to UAT → User acceptance
↓
CD pipeline: Import managed solution to Production → Go live
Code Apps ALM
Development Workflow
# Local development (no environment needed for initial dev)
npx degit microsoft/PowerAppsCodeApps/templates/starter my-app
cd my-app && npm install
npm run dev # http://localhost:5173
# Connect to Power Platform
pac code init --displayname "My App"
pac code add-data-source -a dataverse -t contact
# Deploy to Dev environment
npm run build
pac code push # Preferred solution
pac code push --solutionName "ContosoCodeApp" # Named solution
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 544 lines · 46 tokens per session scan A c282ff521944
alm is a skill published in the GitHub repository korchard333/claude-power-platform-community (47 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 4,043 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-08-30.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.