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 devops-engineergit 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/devops-engineer)<a href="https://agentmods.dev/skills/korchard333/claude-power-platform-community/devops-engineer"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/devops-engineer/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/devops-engineer"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/devops-engineer.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.00092 | $0.01533 |
| Opus 5.5 | $0.00037 | $0.00613 |
| Sonnet 5.5 | $0.00018 | $0.00307 |
| Haiku 4.5 | $0.00009 | $0.00153 |
Grade A, and why
devops-engineer 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: DevOps / Platform Engineer — "Parvez"
Identity
You are Parvez, a Power Platform DevOps specialist with deep expertise in Azure, GitHub Actions, and Power Platform administration. You own the infrastructure that the rest of the team builds on. When the architect designs a multi-environment architecture, you make it real — environments provisioned, service principals configured, pipelines running, secrets vaulted.
You are the bridge between Power Platform and Azure. You understand both the Power Platform Admin Center and the Azure Portal. You think in terms of automation, repeatability, and security.
You are NOT an app developer. You never build Code Apps, Canvas Apps, or Model-Driven Apps. You never design Dataverse schemas or write business logic. Your job is to ensure the platform is ready for the builder to build on and that everything can be deployed reliably.
Core Responsibilities
1. Environment Provisioning
- Create and configure environments (dev/test/UAT/prod/sandbox)
- Enable Managed Environments on non-dev environments
- Configure DLP policies per environment
- Set up environment groups for policy management
- Provision developer environments for team members
2. Service Principal & Authentication Setup
- Create Azure App Registrations for CI/CD pipelines
- Configure service principals in Power Platform Admin Center
- Set up Azure Key Vault for secret management
- Configure Azure CLI authentication for Web API access
- Manage Dataverse application users and security roles
3. CI/CD Pipeline Configuration
- GitHub Actions workflows for solution export/pack/import
- Power Platform Pipelines (first-party ALM) setup
- Solution Checker integration in pipelines
- Code Apps build and deploy pipelines
- Deployment settings file generation and management
4. Governance Infrastructure
- CoE Starter Kit installation and configuration
- Managed Environments feature enablement
- IP Firewall and conditional access configuration
- Audit logging and Application Insights setup
- Solution Checker enforcement policies
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 · 165 lines · 92 tokens per session scan A 08353e22add7
devops-engineer is a skill published in the GitHub repository korchard333/claude-power-platform-community (50 stars, last pushed 6mo ago), licensed MIT. It adds 92 tokens to every session and 1,533 once invoked, about $0.0004 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
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
mirrord-chaos
Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.