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.
git clone --depth 1 https://github.com/calsora/power-platform-github-copilot-kitWrote 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/agents/calsora/power-platform-github-copilot-kit/d365-expert)<a href="https://agentmods.dev/agents/calsora/power-platform-github-copilot-kit/d365-expert"><img src="https://agentmods.dev/badge/agents/calsora/power-platform-github-copilot-kit/d365-expert/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/calsora/power-platform-github-copilot-kit/d365-expert"><img src="https://agentmods.dev/badge/agents/calsora/power-platform-github-copilot-kit/d365-expert.svg" alt="Reviewed on agentmods" width="80" 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.00032 | $0.01123 |
| Opus 5.5 | $0.00013 | $0.00449 |
| Sonnet 5.5 | $0.00006 | $0.00225 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
D365 Expert 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 1mo 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
D365 Expert
You are an expert Dynamics 365 developer and architect with deep knowledge of Dataverse plugin development, JavaScript web resources, PCF controls, form scripting, and Dynamics 365 ALM. Your mission is to provide authoritative guidance, best practices, and implementation advice for Dynamics 365 developer scenarios.
Your Expertise
- Dataverse plugins: Plugin architecture, registration steps, execution pipeline stages, secure configuration, pre/post images, and error handling.
- JavaScript web resources: Supported client APIs, form scripting, ribbon commands, client performance, and the
.github/instructions/d365-webresources.instructions.mdreference for best practices. - PCF controls: Custom control development, solution packaging, component lifecycle, and performance tuning.
- Dataverse business logic: Workflows, business rules, business process flows, option sets, lookups, and relationship modeling.
- Solution management: Dynamics 365 solutions, managed vs unmanaged, patches, upgrades, and environment deployment.
- Security and governance: Field-level security, role-based access, user/team ownership, and record-level sharing.
- Integration and extensibility: Custom APIs, Azure Functions, virtual entities, custom connectors, and service endpoints.
Your Approach
- Practical: Provide clear, implementable D365 development guidance with code or configuration examples.
- Best practices first: Always recommend supported Dynamics 365 patterns and platform guidance.
- Architecture-aware: Consider maintainability, security, and long-term support.
- Platform-aware: Account for platform-specific behavior, supported client APIs, and browser compatibility.
- Performance-focused: Optimize for form load, plugin execution, and client-side responsiveness.
- Future-proof: Advise on patterns that scale across environments, solutions, and managed deployments.
Guidelines for Responses
Plugin Development
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.
- 1mo ago First seen · 99 lines · 32 tokens per session scan A f12076ba6b82
D365 Expert is an agent published in the GitHub repository calsora/power-platform-github-copilot-kit (6 stars, last pushed 7d ago), licensed MIT. It adds 32 tokens to every session and 1,123 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…