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/copilot-instructionsgit 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.01559 | $0.01559 |
| Opus 5 | $0.00779 | $0.00779 |
| Sonnet 5 | $0.00312 | $0.00312 |
| Haiku 4.5 | $0.00156 | $0.00156 |
Grade A, and why
powerplatform-vibecoding-samples copilot-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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for Power Platform Projects
Business Application Project using Microsoft Power Platform. This project will use Microsoft Dataverse as a data platform. This folder wil store :
- Context
- Project context
- Business requirements in agile form
- Functional Flow diagrams
- Architecture & Design principles documentation
- Dataverse data modelisation
- Dataverse security modelisation
- Technical artefacts used in Power Platform Developments
- Unpacked Power Platform solutions
- Power Platform ALM artefacts
- Dataverse Plugins code
- Power Apps PCF code
- Power Apps Code Apps
- Power Pages SPA Websites
Setup
First step when initializing a new project is to fill in the CONTEXT.md file.
Use this instructions to help you fill in the CONTEXT.md file. The file structure is already provided and will not be changed. All data will be provided by the user. The agent will ask the user for missing data.
1. Global Agent Behavior
General Behavior
-
You are an agent: continue working until the user's request is fully resolved. Only end your turn when you're confident the problem is solved and no further action is required.
-
Your thinking should be thorough—it's absolutely fine (and encouraged) if your reasoning is long. Think step by step before and after each action you take.
-
Plan extensively before making any function calls. Reflect critically after each one. Avoid chaining function calls without introspection between them, as that can impair insight and decision-making.
-
If you're unsure about file contents or the codebase structure, use tools to inspect and read relevant files. Never guess or make assumptions.
-
Only make necessary, intentional changes that are either directly requested or clearly required for task completion. Avoid editing unrelated or unclear areas.
Code Quality and Style
-
Prefer simple solutions that are easy to understand and maintain.
-
Avoid code duplication: before writing new logic, check if similar functionality already exists in the codebase.
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 · 167 lines · 1,559 tokens per session scan A dd00840ed2e5
powerplatform-vibecoding-samples copilot-instructions.md is an instructions file published in the GitHub repository tchinnin/powerplatform-vibecoding-samples (6 stars, last pushed 7mo ago), licensed MIT. It adds 1,559 tokens to every session, about $0.0078 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
spec-kit AGENTS.md
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.
vscode buildNext.instructions.md
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).
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.
langchain AGENTS.md
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.
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).
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.