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 agentmods add skills/joshsmithxrm/power-platform-developer-suite/releasenpx skills add joshsmithxrm/power-platform-developer-suite --skill releasegit clone --depth 1 https://github.com/joshsmithxrm/power-platform-developer-suiteWrote 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/joshsmithxrm/power-platform-developer-suite/release)<a href="https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/release"><img src="https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/release.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.07835 |
| Opus 5 | $0.00026 | $0.03918 |
| Sonnet 5 | $0.00010 | $0.01567 |
| Haiku 4.5 | $0.00005 | $0.00783 |
Grade A, and why
release scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://api.nuget.org/v3-flatcontainer/<package-id-lowercase>/index.json | jq '.versions' | tail -5 How it starts
The opening of the file, as written. The whole thing — 629 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
End-to-end release ceremony for PPDS. Produces CHANGELOGs, version bumps, tags, and triggers the CI publishing workflows. Use for prereleases (*-beta.N) and stable releases (1.0.0, 1.1.0, etc.) alike — the mechanics are identical, version suffixes differ.
When to Use
- "Let's cut a release"
- "Time for a new prerelease"
- "Ship v1.0.0"
- "Bump all the packages"
- Scheduled release cadence
Do NOT use this skill for:
- Hot-fix a single package — use
/prand tag that package only - Documentation-only updates — those don't need a release
- Pre-public-release key rotation — that's a separate operation
Usage
/release— default to prerelease flow/release prerelease— explicit prerelease/release stable v1.0.0— stable release, version specified
Prerequisites
Before starting:
- All in-flight PRs are merged or explicitly deferred. Running a release with open feature PRs means either you forget to include them or you rush-merge. Decide first.
- No broken CI on
main. Checkgh run list --branch main --limit 5. If CI is red, fix first. - Security review done for stable releases (enforced). Prereleases can skip; stable (
vX.Y.0) must have a completed/security-reviewartifact atdocs/qa/security-review-*.mdcovering the diff since the last stable release. The pre-merge verification step (Step 6) checks for this file — the release cannot proceed without it. Patches (vX.Y.Zwhere Z > 0) do not require a security review. - Known the last release commit and/or tags. The CHANGELOG enumeration is "since when?". Grab the previous release commit hash:
git log --grep='chore(release)' --oneline -5
Process
1. Register Phase and Create Release Worktree
python scripts/workflow-state.py set phase release
Note:
releaseis a custom phase for this skill. Nothing enforces workflow phases anymore — the workflow-enforcement hooks were extracted with the personal automation harness (#1315) — so the phase registration is purely an audit-trail entry in.workflow/state.json.
What ships with it
1 file 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.
- 4d ago First seen · 629 lines · 52 tokens per session scan A 13f017002347
release is a skill published in the GitHub repository joshsmithxrm/power-platform-developer-suite (5 stars, last pushed 11d ago), licensed MIT. It adds 52 tokens to every session and 7,835 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
release-readiness
Assesses ship-readiness for .NET MAUI release branches — Servicing Releases (SR) and Previews — and produces public-safe, copy-ready release handoffs or Loop-page drafts from the resulting evidence. Use for readiness verdicts, release blockers, Preview/SR status, release handoff pages, manual validation instructions…
create-release
Create a versioned GitHub release with changelog.
bump-version
Bump the SSW.VerticalSliceArchitecture.Template NuGet package version to cut a new release. Use when the user says "bump the version", "cut a release", "release a new version", "publish a new package version", or similar for this template repo. Edits the version in VerticalSliceArchitecture.nuspec — which is what…
release-roslynator
Use when shipping a roslynator release, rolling CHANGELOG.md [Unreleased], updating the VS Code extension changelog, creating a GitHub v release, or optionally tagging cli-v.
maf-release-watcher
Detects new MAF releases, extracts breaking changes, and keeps the toolkit's registry/matrix/guide current. Pipeline: (1) deterministic data extraction via GitHub Actions + Python helpers + dotnet-inspect, opens a PR with raw data and TODOs on a per-version branch (never commits direct to main), (2) optionally, a…
release-cut
Use this skill whenever Larry asks to cut a release (e.g., "prep vX.Y.Z release").