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/agents-mdgit 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.00593 | $0.00593 |
| Opus 5 | $0.00296 | $0.00296 |
| Sonnet 5 | $0.00119 | $0.00119 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
power-platform-github-copilot-kit AGENTS.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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Power Platform Reusable Repo - Agent Guidance
This repo is designed to support reusable Power Platform delivery with clear structure, automation, and agent-driven guidance.
Goal
Create a repo that is easy for teams to reuse across Power Apps, Power Automate, Dataverse, connectors, and Azure-integrated solutions.
Agent usage guidance
This file should document how contributors and AI agents collaborate in this repo.
Recommended agent roles
-
Power Platform Architect- design solution architecture and reuse patterns
- define Dataverse strategy, app topology, environment structure
- align governance and platform rules
-
Power Platform Expert- answer implementation questions for Power Apps, Power Automate, connectors, and Dataverse
- recommend reusable components and low-code best practices
-
DevOps Expert- design CI/CD pipelines and automation for ALM
- recommend Power Platform CLI, GitHub Actions, or Azure DevOps templates
- support environment promotion and solution deployment
-
Azure Principal Architect- advise on Azure integration, identity, security, and platform boundary patterns
- map Power Platform connectivity to Azure services and enterprise architecture
-
D365 Expert- provide Dynamics 365 development guidance for plugins, JavaScript web resources, PCF controls, and Dataverse business logic
- use
.github/instructions/d365-webresources.instructions.mdas the canonical web resource best-practice reference
-
Explore- search repo contents and identify where to place new artifacts
- help contributors find relevant docs, templates, and sample solutions
How to use this file
- Add new agent guidance whenever you add a new role or workflow.
- Link agent responsibilities to repo folders and topics.
- Use this file as the canonical place for contributor-facing agent instructions.
What to document here
- the purpose of each agent role
- when to ask each agent for help
- where new files should be placed in the repo
- how to keep documentation, templates, and automation aligned
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 · 73 lines · 593 tokens per session scan A 1c62a954757b
power-platform-github-copilot-kit AGENTS.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 593 tokens to every session, about $0.0030 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
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.