agentmods.dev

PowerPlatform-DataversePlugins

Project instructions for building Dataverse plugins in C#. Dataverse is Microsoft's cloud data platform, and a plugin is server-side code that runs when data or business events occur.

In plain words
What is it for?
Use them to create and organize C# plugins, generate data classes, configure project files, and deploy plugins with Power Platform CLI instead of the Plugin Registration Tool.
Why use it?
They define the required project structure, generated base class, package-based deployment, and development workflow, reducing setup mistakes and inconsistent plugins.

Instructions file for GitHub Copilot

6 7mo ago A scan 4,411 tokens original MIT
View the source file tchinnin/powerplatform-vibecoding-samples
Install

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.

agentmods
npx agentmods add instructions/tchinnin/powerplatform-vibecoding-samples/powerplatform-dataverseplugins
Clone the repo
git clone --depth 1 https://github.com/tchinnin/powerplatform-vibecoding-samples

Made for: GitHub Copilot.

Per session 4,411 This file is loaded in full into every session.
When invoked 4,411 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.04411 $0.04411
Opus 5 $0.02205 $0.02205
Sonnet 5 $0.00882 $0.00882
Haiku 4.5 $0.00441 $0.00441

Measured yesterday against content hash dd6fc847df7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

PowerPlatform-DataversePlugins 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.

.github/instructions/PowerPlatform-DataversePlugins.instructions.md · 516 lines

How it starts

The opening of the file, as written. The whole thing — 516 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Copilot Instructions for Dataverse Plugin Development

These are special instructions for GitHub Copilot (Agent Mode) to follow when helping with Dataverse plugin development.

📌 Project Context

  • This repository is for Dataverse plugin development.
  • The code is written in C# (.NET Framework 4.6.2).
  • Plugins are deployed as NuGet packages using Power Platform CLI (PAC), not Plugin Registration Tool (PRT).
  • The project uses early bound classes generated with pac modelbuilder build.
  • We use Visual Studio Code as the main IDE.
  • CRITICAL: Always use pac plugin init to create plugin projects and ensure all plugins extend the generated PluginBase.cs class.

📁 Project Structure

Each plugin project should follow this standard folder structure:

Plugins/
└── {ProjectName}/
    ├── {ProjectName}.csproj          # Project file with NuGet package configuration
    ├── {ProjectName}.snk             # Strong name key file for assembly signing
    ├── PluginBase.cs                 # Generated base class from pac plugin init
    ├── Models/                       # Early-bound entity classes
    │   ├── Entities/                 # Generated entity classes
    │   ├── OptionSets/               # Generated option set classes
    │   └── EntityOptionSetEnum.cs    # Option set enumeration
    ├── Helpers/                      # Reusable helper classes
    │   ├── EnvironmentVariableHelper.cs
    │   ├── BusinessUnitHelper.cs
    │   ├── TeamHelper.cs
    │   ├── SecurityRoleHelper.cs
    │   └── CommonHelper.cs
    └── Plugins/                      # Plugin implementations
        ├── EntityNameCreatePlugin.cs
        ├── EntityNameUpdatePlugin.cs
        └── ...

Project File (.csproj) Configuration

The .csproj file must include:

  • Target Framework: net462
  • Assembly Signing: Strong name key file
  • NuGet Package Configuration: PackageId, Version, Authors, Company, Description
  • Required NuGet Packages:
    • Microsoft.CrmSdk.CoreAssemblies (version 9.0.2.*)
    • Microsoft.PowerApps.MSBuild.Plugin (version 1.*)
    • Microsoft.NETFramework.ReferenceAssemblies (version 1.0.*)

Read the full file on GitHub · 516 lines

Changes

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.

  1. yesterday First seen · 516 lines · 4,411 tokens per session scan A dd6fc847df7c

Subscribe to this mod's changes

PowerPlatform-DataversePlugins is an instructions file published in the GitHub repository tchinnin/powerplatform-vibecoding-samples (6 stars, last pushed 7mo ago), licensed MIT. It adds 4,411 tokens to every session, about $0.0221 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.

Backend and APIsDevOps and cloudProductivity
Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,040 tokens

langchain AGENTS.md

Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens