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/calsora/power-platform-github-copilot-kit/d365-webresourcesgit clone --depth 1 https://github.com/calsora/power-platform-github-copilot-kitWhat 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.01295 | $0.01295 |
| Opus 5 | $0.00647 | $0.00647 |
| Sonnet 5 | $0.00259 | $0.00259 |
| Haiku 4.5 | $0.00129 | $0.00129 |
Grade A, and why
power-platform-github-copilot-kit d365-webresources.instructions.md 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 2d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dynamics 365 JavaScript Web Resource Best Practices
This guidance describes reusable patterns and anti-patterns for client-side JavaScript used in Dynamics 365 / Power Platform web resources.
Severity levels:
- CRITICAL — Code that creates functional failure, security risk, or unsupported behavior in Dynamics 365.
- IMPORTANT — Code that reduces maintainability, performance, or compatibility with platform upgrades.
- SUGGESTION — Improvements for readability, tooling, or developer experience.
Core principles
- Use supported client API and avoid unsupported DOM or internal Xrm object access.
- Keep business logic out of web resources when possible; prefer Power Fx, business rules, plugins, or Power Automate for process logic.
- Build modular, testable JavaScript with clear namespace/closure boundaries.
- Use solution-aware web resources and version them with solution layering.
- Optimize for performance on form load and ribbon actions.
Supported API and platform compatibility
| Rule | Summary | Severity |
|---|---|---|
Use formContext instead of global Xrm.Page |
Xrm.Page is deprecated. Use the execution context to get the form context. |
IMPORTANT |
| Avoid unsupported DOM selectors | Do not query or modify DOM elements directly with document.querySelector or getElementById. |
CRITICAL |
| Use supported client-side events only | Register code through form event handlers or ribbon commands, not by attaching custom DOM listeners to internal controls. | IMPORTANT |
| Avoid proprietary browser APIs | Target the browser support model for Dynamics 365 and avoid APIs not supported by supported browsers. | SUGGESTION |
Code structure anti-patterns (C1-C5)
C1: Global variables without namespace
- Severity: IMPORTANT
- Detection:
var myValue = ...orwindow.myValuein a web resource. - Use a single namespace object or Immediately Invoked Function Expression (IIFE) to avoid collisions.
// GOOD
var MyApp = MyApp || {};
MyApp.ContactForm = {
onLoad: function (executionContext) {
var formContext = executionContext.getFormContext();
}
};
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.
- 2d ago First seen · 141 lines · 1,295 tokens per session scan A 634f2179e5e4
power-platform-github-copilot-kit d365-webresources.instructions.md is an instructions file published in the GitHub repository calsora/power-platform-github-copilot-kit (6 stars, last pushed 2mo ago), licensed MIT. It adds 1,295 tokens to every session, about $0.0065 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 instructions, from other repositories
Browser4 CLAUDE.md
Instructions for platonai/Browser4, covering browser4 — project context for claude, architecture, key dispatch chain (cli → browser), batch commands and e2e test structure.
spring-ai-agentcore AGENTS.md
Instructions for spring-ai-community/spring-ai-agentcore, covering agents.md, project overview, architecture, key components and artifact store classes.
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
deckforge AGENTS.md
Instructions for tph-kds/deckforge, covering deckforge agent entry point, code intelligence, read order, default routing and non-negotiable implementation rules.
fast-browser CLAUDE.md
Claude Code instructions for m4ttstack/fast-browser, covering fast browser plugin, where a change belongs, fork branch: use fast-browser-runtime, releasing a new runtime and re-pinning this repo: use the script.
agentoscope AGENTS.md
Instructions for rafaelcg/agentoscope, covering agentoscope — agent instructions, what this is, layout, commands and conventions.