Borrowing it
Nothing to install: this file belongs to Hack23/European-Parliament-MCP-Server. 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/Hack23/European-Parliament-MCP-Server/main/.github/skills/security-by-design/SKILL.mdgit clone --depth 1 https://github.com/Hack23/European-Parliament-MCP-ServerWrote 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/skills/hack23/european-parliament-mcp-server/security-by-design)<a href="https://agentmods.dev/skills/hack23/european-parliament-mcp-server/security-by-design"><img src="https://agentmods.dev/badge/skills/hack23/european-parliament-mcp-server/security-by-design/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/skills/hack23/european-parliament-mcp-server/security-by-design"><img src="https://agentmods.dev/badge/skills/hack23/european-parliament-mcp-server/security-by-design.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.00028 | $0.06793 |
| Opus 5.5 | $0.00011 | $0.02717 |
| Sonnet 5.5 | $0.00006 | $0.01359 |
| Haiku 4.5 | $0.00003 | $0.00679 |
Grade A, and why
security-by-design 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.
This is a copy
88% identical to incident-response — 979 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 943 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security By Design Skill
Context
This skill applies when:
- Implementing MCP protocol tools and handlers
- Exposing European Parliament data through APIs
- Handling user inputs or external data sources
- Implementing authentication or authorization mechanisms
- Processing sensitive or classified information
- Designing rate limiting or abuse prevention
- Implementing audit logging and monitoring
- Writing security-critical validation logic
- Handling errors and exceptions securely
- Configuring network security or TLS
Security is foundational, not optional. Every feature must be designed with security in mind from the start, following the principle of "secure by default" and implementing defense-in-depth strategies aligned with Hack23 AB's ISMS policies.
Rules
- Never Trust Input: Validate and sanitize all user inputs - treat everything as potentially malicious
- Fail Securely: Systems must fail to a secure state, never expose sensitive information in errors
- Principle of Least Privilege: Grant minimal permissions required for functionality, nothing more
- Defense in Depth: Implement multiple overlapping security controls (validation + rate limiting + audit logging)
- Encrypt Everything: Use TLS 1.3+ for transit, AES-256 for at rest, never store secrets in plaintext
- Audit All Actions: Log authentication attempts, authorization failures, input validation errors
- Rate Limit Aggressively: Protect against abuse, DoS attacks, and resource exhaustion
- Validate Schema: Use strict schema validation for all MCP tool inputs and outputs
- Sanitize Output: Encode data appropriately to prevent injection attacks (XSS, command injection)
- Secure Defaults: All features must be secure by default, require opt-in for permissive settings
- No Secrets in Code: Never commit API keys, tokens, or credentials to source control
- Regular Updates: Keep dependencies updated, scan for vulnerabilities continuously
- Assume Breach: Design systems assuming attackers will get in - limit blast radius
- Document Security: Reference ISMS policies, document threat models and security controls
- Test Security: Write tests for authentication, authorization, input validation, and error handling
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 · 943 lines · 28 tokens per session scan A 4e5d5e31ff53
security-by-design is a skill published in the GitHub repository Hack23/European-Parliament-MCP-Server (29 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 6,793 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to incident-response, differing in 979 lines, and is treated as a copy.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
frontmcp-setup
Use when starting, scaffolding, or organizing a FrontMCP project. Covers creating a new project (CLI scaffold or manual) for Node, Vercel, and other targets; standalone versus Nx-monorepo layout, naming conventions, generators, and dependency rules; composing multiple @App classes, ESM packages, and remote MCP servers…
x-use-review
Daily digest for an x-use account covering health, metrics, pending drafts, and queued work in one pass, then approve/reject/process per the user's direction. Use for "how is my account doing", daily check-ins, or before any batch of approvals.