Borrowing it
Nothing to install: this file belongs to webmaxru/is-ai-native. 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/webmaxru/is-ai-native/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/webmaxru/is-ai-nativeWrote 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/webmaxru/is-ai-native/copilot-instructions)<a href="https://agentmods.dev/instructions/webmaxru/is-ai-native/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/webmaxru/is-ai-native/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/webmaxru/is-ai-native/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/webmaxru/is-ai-native/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.00316 | $0.00316 |
| Opus 5.5 | $0.00126 | $0.00126 |
| Sonnet 5.5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
is-ai-native 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.
What it actually says
- For design and frontend related tasks, always use Playwright MCP for making resulting screenshots and always attach these screenshots to the PR description.
- Put all made screenshots ONLY in a folder named
artifactsat the root of the repository. - For every change of the logic, configuration, user experience make sure you checked and updated web application, vs code extension, and github cli extension.
- For every change to configuration files or configuration documentation, make sure saved agents and saved prompts under
.github/agentsand.github/promptsstay in sync with the current file paths, workflows, and source-of-truth references. - Keep
.env.examplestructurally aligned with the root.env: same keys, same ordering, and same explanatory comments, but never copy real secret values into.env.example. - For README reviews and updates, prioritize product consumption and end-user workflows before contributor workflows.
- In the root README, start with the project description and mention the web app, VS Code extension, GitHub CLI extension, and standalone CLI at the beginning.
- In the root README, list shared cross-surface capabilities before web app specific details.
- In the root README, link to the VS Code extension, GitHub CLI extension, and standalone CLI READMEs instead of duplicating their full usage documentation.
- Keep the root README, standalone CLI README, GitHub CLI extension README, and VS Code extension README aligned in overall structure and writing style.
- Move local development, release engineering, packaging, and other contributor-focused material to the bottom of each README.
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 · 11 lines · 316 tokens per session scan A e555a809ce92
is-ai-native copilot-instructions.md is an instructions file published in the GitHub repository webmaxru/is-ai-native (5 stars, last pushed 2mo ago), licensed MIT. It adds 316 tokens to every session, about $0.0013 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.