Borrowing it
Nothing to install: this file belongs to sidrat2612/agent-policykit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sidrat2612/agent-policykit/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/sidrat2612/agent-policykitWrote 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/instructions/sidrat2612/agent-policykit/copilot-instructions)<a href="https://agentmods.dev/instructions/sidrat2612/agent-policykit/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sidrat2612/agent-policykit/copilot-instructions/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/instructions/sidrat2612/agent-policykit/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sidrat2612/agent-policykit/copilot-instructions.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.05039 | $0.05039 |
| Opus 5.5 | $0.02016 | $0.02016 |
| Sonnet 5.5 | $0.01008 | $0.01008 |
| Haiku 4.5 | $0.00504 | $0.00504 |
Grade A, and why
agent-policykit 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 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 — 524 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source of Truth
The Miro board is the single source of truth for all product, design, and architecture decisions:
- Board URL: https://miro.com/app/board/uXjVHSJQ-Eg=/
- Never guess or assume project-specific details (features, specs, data, numbers, flows, designs)
- Check the extracted docs first in
docs/before answering questions about the product - If the required information is missing, ambiguous, or not covered in
docs/, then check the Miro board using MCP tools (context_explore,context_get,table_list_rows) - If the information is not present on the Miro board, ask the user — do not fabricate or approximate
Project Context
- Platform: Life-Path Mapping Platform for Indian students (14–24)
- Stack: Next.js (web), React Native + Expo (mobile), NestJS (backend), PostgreSQL, Redis
- Docs folder:
docs/contains extracted specs from Miro (numbered 01–21) - Treat student data and any under-18 user flows as high-scrutiny from a privacy, consent, retention, and access-control perspective
Theme Governance
- The finalized Professional Growth Palette is the source of truth for all visual theme work across the website, webapp frontend, and mobile frontend.
- Theme tokens must be maintained centrally. Do not define brand, track, semantic, or status colors inside individual pages or components.
- Website theme sources must remain centralized in the shared website theme files and token roots.
- Webapp frontend theme sources must remain centralized in the shared webapp theme files and token roots.
- Mobile frontend theme sources must follow the same rule: maintain one central theme source and consume it everywhere.
- If a new visual state or color is needed, add it to the central theme first, then consume that token in pages and components.
- Avoid hardcoded hex values and ad hoc Tailwind utility colors for brand or semantic styling when a centralized token should exist.
Engineering Governance Standard
These instructions govern code generation, refactoring, reviews, infrastructure automation, CI/CD, prompts, queries, architecture proposals, and other AI-assisted engineering work in this repository.
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 · 524 lines · 5,039 tokens per session scan A 7c601c97067c
agent-policykit copilot-instructions.md is an instructions file published in the GitHub repository sidrat2612/agent-policykit (5 stars, last pushed 5mo ago), licensed MIT. It adds 5,039 tokens to every session, about $0.0202 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 instructions, from other repositories
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).
next.js AGENTS.md
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, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.