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/specnpx skills add joshsmithxrm/power-platform-developer-suite --skill specgit 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/spec)<a href="https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/spec"><img src="https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/spec.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.00003 | $0.01101 |
| Opus 5 | $0.00002 | $0.00550 |
| Sonnet 5 | $0.00001 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
spec 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 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.
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec
Create, update, or reconcile a specification following PPDS conventions. Three modes: forward (create new), update (modify existing), reconcile (align spec with code). Ensures consistency, cross-references related specs, and enforces numbered acceptance criteria.
Input
$ARGUMENTS = spec name (e.g., connection-pooling for existing, new-feature for new)
Process
Step 1: Load Foundation
Read these files before doing anything else:
specs/CONSTITUTION.md— non-negotiable principles (includes Spec Laws SL1–SL5)specs/SPEC-TEMPLATE.md— structural template- Glob
specs/*.mdand grep each for**Code:**lines to build a code-path-to-spec map. This replaces the README index.
Step 2: Determine Mode
Forward mode — spec does not exist (specs/$ARGUMENTS.md not found):
- Search existing specs for overlapping scope — check that this isn't already covered
- If overlap found, ask user: update existing spec or create new one?
- Proceed to authoring (Step 4)
Update mode — spec exists, user requests specific changes:
- Read the existing spec
- Read the code files referenced in the spec's
Code:header line - Identify drift: does the code match what the spec describes?
- Identify missing ACs: does the spec have numbered acceptance criteria?
- Present findings to user before making changes
- Proceed to authoring (Step 4)
Reconcile mode — spec exists, user wants to align spec with code (/spec <name> --reconcile or when significant code divergence is detected):
- Read the existing spec and extract all ACs, Code paths, and type descriptions
- Read the code at the spec's
Code:paths - Enumerate public types, methods, and behaviors in the code
- Compare against existing ACs:
- Missing ACs: Code behavior with no corresponding AC → propose new ACs
- Stale ACs: AC describes behavior the code no longer has → flag for removal
- Status drift: AC references a test that now passes/fails differently → flag for update
- Member-count verification: Count public types/methods in code, count ACs. Report the delta. If ACs cover less than 90% of public surface area, warn explicitly. This prevents the known LLM summarization problem (capturing ~70-80% and missing the rest).
- Compare spec prose (Architecture, Core Requirements) against actual code structure
- Present all proposed changes to user for approval before writing
- After writing: regenerate README, append to Changelog
- Skip to Step 6 (reconcile does not go through the authoring flow)
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 · 96 lines · 3 tokens per session scan A fd04dab83366
spec is a skill published in the GitHub repository joshsmithxrm/power-platform-developer-suite (5 stars, last pushed 11d ago), licensed MIT. It adds 3 tokens to every session and 1,101 once invoked, about $0.0000 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-31.
Other skills, from other repositories
PowerAppsControl
Drive the PowerAppsControl MCP server to UX-test a Power App end to end: open and verify an app URL, let the user choose a mode (smoke test = in-depth read-only exploration that produces a repeatable natural-language test plan; or run my test plan), then run it in a recorded session and produce a video + HTML report…
xrm-mcp
Skip steps you already have answers for. If you ran listtables or describetable earlier in the session, reuse those results.
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…