Borrowing it
Nothing to install: this file belongs to the-missing-pink/ai-repository-security-baseline. 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/the-missing-pink/ai-repository-security-baseline/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/the-missing-pink/ai-repository-security-baselineWrote 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/the-missing-pink/ai-repository-security-baseline/copilot-instructions)<a href="https://agentmods.dev/instructions/the-missing-pink/ai-repository-security-baseline/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/the-missing-pink/ai-repository-security-baseline/copilot-instructions.svg" alt="Measured on agentmods" 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.00487 | $0.00487 |
| Opus 5 | $0.00244 | $0.00244 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
ai-repository-security-baseline 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 8d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions
Read and follow all rules in AGENTS.md — it is the central source of truth for this repository.
Security Rules
- NEVER suggest code that hardcodes secrets, API keys, tokens, or passwords.
- NEVER suggest reading from or writing to
.envfiles (.env.exampleis allowed). - NEVER generate code that constructs SQL queries via string concatenation — use parameterized queries.
- NEVER suggest
eval(),exec(), or equivalent dynamic code execution with user input. - NEVER suggest disabling SSL/TLS verification or security headers.
- Always suggest input validation at system boundaries.
- Always suggest output encoding to prevent XSS.
- Flag any pattern that matches common secret formats (API keys, tokens, connection strings).
Privacy Rules
- Never suggest logging PII (names, emails, IP addresses, phone numbers).
- Suggest data masking or redaction when PII must appear in output.
- Prefer anonymous or pseudonymous identifiers over PII.
- Suggest consent mechanisms when generating data collection code.
Code Quality
- Follow existing patterns and conventions found in the codebase.
- Suggest typed code (TypeScript over JavaScript, type hints in Python, etc.).
- Suggest error handling for all fallible operations.
- Prefer well-established libraries over obscure ones.
- Suggest tests alongside new functions and methods.
Accessibility
- Use semantic HTML elements in suggestions.
- Include ARIA attributes where appropriate.
- Ensure interactive elements are keyboard accessible.
- Maintain proper heading hierarchy.
- Suggest adequate color contrast values.
Testing
- Suggest tests for new functions and methods.
- Include edge cases and error paths in test suggestions.
- Use mocks for external services.
- Follow the Arrange-Act-Assert pattern.
Dependencies
- Only suggest well-known, widely-used packages.
- Prefer packages with active maintenance and large user bases.
- Check package names carefully — avoid typosquatting.
- Always suggest exact version pinning.
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.
- 8d ago First seen · 61 lines · 487 tokens per session scan A 5fb55ecefc34
ai-repository-security-baseline copilot-instructions.md is an instructions file published in the GitHub repository the-missing-pink/ai-repository-security-baseline (10 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 487 tokens to every session, about $0.0024 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
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.
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.
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).
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).
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.
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.