microsoft/Dataverse-skills is a collection of skills that lets AI coding agents build, query, deploy, and administer Microsoft Dataverse environments and linked Dynamics 365 Finance and Operations systems. It is for working with Dataverse data models, records, solutions, and Finance and Operations development through natural-language instructions. The catalogue entries are the skills and plugin that operate the Dataverse tools and workflows.
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/microsoft/dataverse-skills/erp-xppnpx skills add microsoft/Dataverse-skills --skill erp-xppgit clone --depth 1 https://github.com/microsoft/Dataverse-skillsWrote 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/microsoft/dataverse-skills/erp-xpp)<a href="https://agentmods.dev/skills/microsoft/dataverse-skills/erp-xpp"><img src="https://agentmods.dev/badge/skills/microsoft/dataverse-skills/erp-xpp.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.1 | $0.00084 | $0.03399 |
| Opus 5 | $0.00042 | $0.01699 |
| Sonnet 5 | $0.00017 | $0.00680 |
| Haiku 4.5 | $0.00008 | $0.00340 |
Grade A, and why
erp-xpp 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 yesterday.
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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Finance and Operations X++ Development
Critical safety rules — read first
- Windows only.
pac tool xpp installandpac package compile --package-type erprequire Windows. Do not invent a Linux/macOS or SDK-based fallback.- Confirm the target before any deploy or DB sync. Show the Dataverse environment URL, obtain explicit confirmation, then run
pac org who --environment <url>and verify both the Dataverse URL and linked ERP URL/version.- Never assume Full DB sync. Although standalone
pac package db-syncdefaults toFull, require the user to chooseFull,Module, orIncrementalwhen the request is ambiguous.- Do not call deployment successful until PAC reaches a successful terminal state. Preserve and report the async operation ID on failure.
- Do not overwrite existing models or source files. Inspect
.erp/xpp.json, descriptors, and target metadata paths before scaffolding or editing.- Pin every runtime surface before ERP verification. PAC and the Dataverse CLI have separate active profiles. Before any
dataverse ... --target erpcheck, requiredataverse auth whoanddataverse org who --jsonto match the confirmed Dataverse and linked ERP URLs. Validate ERP MCP according to its transport: direct HTTP must target<erp-url>/mcp; an stdio proxy must receive the base<erp-url>and route effectively to/mcp. Profile selection does not retarget an existing MCP connection.- Treat runtime verification as possible data mutation. After the separate post-deployment opt-in, inspect the X++ implementation, disclose exact test inputs and expected mutations, and obtain confirmation for those inputs and effects. Do not apply a generic test matrix to non-idempotent operations.
- All additional validation after an ERP X++ package deployment is opt-in. After
pac package deploy --package-type erp, capture PAC's terminal result, then ask whether the user wants any further validation and which checks to run. Do not query the async operation, execute an X++ artifact, query its ERP entity, or test its security unless selected. For runtime validation, confirm exact inputs, success criteria, and failure criteria; never invent values or execute an unapproved failure path. This rule is scoped to ERP X++ package deployment, not Dataverse solution ALM.
PAC CLI is the managed surface for the X++ lifecycle. Do not replace these commands with raw Dataverse APIs, direct calls to the ERP sidecar, LCS upload automation, or hand-written compiler invocations.
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.
- yesterday First seen · 186 lines · 84 tokens per session scan A 8a5360e947c2
erp-xpp is a skill published in the GitHub repository microsoft/Dataverse-skills (216 stars, last pushed 2d ago), licensed MIT. It adds 84 tokens to every session and 3,399 once invoked, about $0.0004 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-09-05.
Other skills, from other repositories
xrm-mcp
Skip steps you already have answers for. If you ran listtables or describetable earlier in the session, reuse those results.
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
kalshi-api
Kalshi exchange mechanics — RSA-PSS auth, order schema, YES/NO orderbook convention, WebSocket, and endpoint surface. Market-type-agnostic shared layer for all Kalshi skills.
ib-collar
Generate tactical collar strategy reports for protecting PMCC positions through earnings or high-risk events. Requires TWS or IB Gateway running locally.
report-stock
Generate comprehensive stock analysis report (PDF or markdown) with trend, PMCC, and fundamental analysis.