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/kevinrabun/gdprshiftleftmcp/copilot-instructionsgit clone --depth 1 https://github.com/KevinRabun/GDPRShiftLeftMCPWrote 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/kevinrabun/gdprshiftleftmcp/copilot-instructions)<a href="https://agentmods.dev/instructions/kevinrabun/gdprshiftleftmcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/kevinrabun/gdprshiftleftmcp/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 | $0.01067 | $0.01067 |
| Opus 5 | $0.00534 | $0.00534 |
| Sonnet 5 | $0.00213 | $0.00213 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
GDPRShiftLeftMCP 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 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
These instructions guide GitHub Copilot (and similar AI tools) when contributing to the GDPRShiftLeftMCP open‑source project.
This project provides a GDPR‑aware “shift‑left” compliance automation MCP server.
Copilot must always prioritize correctness, accuracy, automated test coverage, functional validation, security, and data protection over speed.
1. Project Priorities
1.1 Correctness & Accuracy
- All generated code must be correct, deterministic, and align with GDPR requirements.
- No speculative interpretations of GDPR are allowed.
- Ambiguous requirements must trigger a request for clarification.
1.2 Security by Default
- Follow industry best practices including least privilege, secure defaults, and input validation.
- Never emit code that logs or stores personal data.
- Ensure GDPR principles (minimization, confidentiality, purpose limitation, etc.) are respected.
1.3 Comprehensive Automated Testing
- Every new feature must include automated unit, integration, or behavior‑driven tests.
- All code-paths, including edge cases and failure scenarios, must be tested.
- Tests must run deterministically across environments.
- Copilot must suggest test cases when writing or modifying code.
2. Code Quality Standards
2.1 Clarity & Maintainability
- Prefer clear and explicit solutions over clever optimizations.
- Document all core modules and public interfaces with docstrings and explanations.
2.2 Dependency Management
- Prefer stable, audited, actively maintained libraries.
- Avoid unnecessary or experimental dependencies.
3. GDPR‑Specific Requirements
3.1 No Personal Data in Examples
Use placeholders only.
3.2 No Logging of Personal or Sensitive Data
All logging must follow GDPR privacy‑by‑design principles.
3.3 Faithful Implementation of GDPR Concepts
GDPR logic (DSRs, DPIAs, Article 30 ROPA, etc.) must be implemented precisely based on documented requirements.
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 · 171 lines · 1,067 tokens per session scan A 0e1f60e83515
GDPRShiftLeftMCP copilot-instructions.md is an instructions file published in the GitHub repository KevinRabun/GDPRShiftLeftMCP (2 stars, last pushed 6mo ago), licensed MIT. It adds 1,067 tokens to every session, about $0.0053 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
klaws CLAUDE.md
Claude Code instructions for rostradamus/klaws, covering claude.md, about, critical rules, build & test and architecture.
mcp-nsa AGENTS.md
AGENTS.md instructions for matematicsolutions/mcp-nsa, covering agents.md - mcp-nsa, project goal, matematic context (hard constraints), mcp tools (tools contract) and build and test.
ClauseKeeper clause-rules.instructions.md
Instructions for mityda/ClauseKeeper, covering clause rules and scanner instructions, rule structure, adding a jurisdiction or new legal regime safely and scanner engine expectations.
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.