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/thiagoguislotti/copilot-instructions/security-vulnerabilitiesgit clone --depth 1 https://github.com/ThiagoGuislotti/copilot-instructionsWrote 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/thiagoguislotti/copilot-instructions/security-vulnerabilities)<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/security-vulnerabilities"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/security-vulnerabilities.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 | $0.01367 | $0.01367 |
| Opus 5 | $0.00683 | $0.00683 |
| Sonnet 5 | $0.00273 | $0.00273 |
| Haiku 4.5 | $0.00137 | $0.00137 |
Grade A, and why
copilot-instructions security-vulnerabilities.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 4d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Standards Baseline
- Use this instruction for API, frontend, backend, and database security decisions.
- Prioritize prevention of OWASP Top 10 and API Top 10 classes of vulnerabilities.
- Treat this as a secure-by-default baseline, then add domain-specific controls as needed.
Current Reference Standards
- OWASP ASVS 5.0.0 as the application security verification baseline.
- OWASP API Security Top 10 2023 for API-specific threat classes.
- OWASP Top 10 2021 (v1.1 released July 13, 2025) for web application risk coverage.
- NIST SP 800-218 SSDF v1.1 for secure software development lifecycle practices.
- NIST SP 800-63B-4 for authentication and authenticator lifecycle controls.
- NIST SP 800-53 Rev 5 control families for governance alignment.
- CWE Top 25 current release for recurring weakness prioritization.
Cross-Layer Secure-by-Default Rules
- Enforce least privilege for identities, services, data access, and runtime permissions.
- Enforce deny-by-default authorization and explicit allow rules per action.
- Validate all untrusted input at trust boundaries and normalize before use.
- Encode output by context to prevent injection and data interpretation flaws.
- Keep secrets out of source code and logs; use managed secret stores and short-lived credentials.
- Encrypt sensitive data in transit and at rest with managed key rotation.
- Require structured audit logging with correlationId and immutable retention policy.
API Security Controls
- Enforce object-level and function-level authorization on every endpoint and resource ID.
- Use strong authentication with scoped tokens and explicit token audience validation.
- Validate request and response contracts with strict schemas; reject unknown or unsafe fields.
- Enforce rate limits, quotas, and abuse controls for sensitive business flows.
- Apply request size limits, timeout limits, pagination caps, and payload depth limits.
- Prevent SSRF with strict outbound allowlists, DNS rebinding defenses, and blocked link-local targets.
- Protect file upload endpoints with type validation, malware scanning, and storage isolation.
- Expose only required API versions and maintain a complete endpoint inventory.
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.
- 4d ago First seen · 105 lines · 1,367 tokens per session scan A 8ca5dbf503a9
copilot-instructions security-vulnerabilities.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 1,367 tokens to every session, about $0.0068 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
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).
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.
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.