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 instructions/tchinnin/powerplatform-vibecoding-samples/powerplatform-dataversepluginsdocgit clone --depth 1 https://github.com/tchinnin/powerplatform-vibecoding-samplesWhat 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.02860 | $0.02860 |
| Opus 5 | $0.01430 | $0.01430 |
| Sonnet 5 | $0.00572 | $0.00572 |
| Haiku 4.5 | $0.00286 | $0.00286 |
Grade C, and why
PowerPlatform-DataversePluginsDoc scanned grade C 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 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
6. Extract environment variables referenced How it starts
The opening of the file, as written. The whole thing โ 460 lines โ stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions for Dataverse Plugin Documentation
These instructions guide the agent in documenting Dataverse .NET plugins developed in the codebase.
๐ Documentation Context
- This documentation is for Dataverse C# Plugin projects
- Each plugin project is located under
Plugins/{ProjectName}/ - Projects contain:
Helpers/- Reusable helper classesPlugins/- Plugin implementations (standard messages or custom APIs){ProjectName}.csproj- Project file with NuGet configuration
๐ Documentation Structure
Each plugin project should have three markdown documentation files in its root folder:
Plugins/
โโโ {ProjectName}/
โโโ README.md # Global project documentation with table of contents
โโโ HELPERS.md # Helper classes documentation
โโโ PLUGINS.md # Plugin implementations documentation
โโโ Helpers/ # Helper source code
โโโ Plugins/ # Plugin source code
โโโ {ProjectName}.csproj # Project file
๐ Documentation Files Structure
1. README.md - Global Project Documentation
This is the main entry point for the plugin project documentation.
Structure:
# {Project Name} - Dataverse Plugin Package
## Overview
Brief description of the project purpose and scope.
## Package Information
| Property | Value |
|----------|-------|
| **Package ID** | {PackageId from .csproj} |
| **Version** | {Version from .csproj} |
| **Authors** | {Authors from .csproj} |
| **Company** | {Company from .csproj} |
| **Target Framework** | net462 |
| **Assembly Signing** | Yes (.snk) |
## Dependencies
### NuGet Packages
- `Microsoft.CrmSdk.CoreAssemblies` - Version X.X.X
- `Microsoft.PowerApps.MSBuild.Plugin` - Version X.X.X
- `Microsoft.NETFramework.ReferenceAssemblies` - Version X.X.X
### Dependent Assemblies
List any additional assemblies included in the package (if applicable).
## Documentation
### [Helper Classes](HELPERS.md)
- [HelperName1](HELPERS.md#helpername1)
- [HelperName2](HELPERS.md#helpername2)
- ...
### [Plugin Implementations](PLUGINS.md)
- [PluginName1](PLUGINS.md#pluginname1)
- [PluginName2](PLUGINS.md#pluginname2)
- ...
## Deployment
This package is deployed using Power Platform CLI:
\`\`\`sh
pac plugin push --pluginId {PluginPackageId} --pluginFile ./bin/Release/{ProjectName}.{Version}.nupkg
\`\`\`
**Note:** The plugin package ID is provided by the user after initial import into the environment.
## Environment Variables
List of required environment variables (if applicable):
- `env_VariableName1` - Description
- `env_VariableName2` - Description
## Prerequisites
- Dataverse environment with required tables
- Security roles configured
- Environment variables configured
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 ยท 460 lines ยท 2,860 tokens per session scan C 096f57d52059
PowerPlatform-DataversePluginsDoc is an instructions file published in the GitHub repository tchinnin/powerplatform-vibecoding-samples (6 stars, last pushed 7mo ago), licensed MIT. It adds 2,860 tokens to every session, about $0.0143 per session on Opus 5. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
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).
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.
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).
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.
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.