European-Parliament-MCP-Server: Skill for Claude Code

.github/skills/secure-development-lifecycle/SKILL.md

secure-development-lifecycle is a skill for Claude Code, Codex from Hack23/European-Parliament-MCP-Server. It costs 33 tokens per session (945 once invoked), scanned A, original, Apache-2.0.

A set of security practices for the software development life cycle, covering work from requirements and design through coding, testing, and deployment. It is focused on TypeScript and Node.js MCP servers and includes common security standards such as OWASP Top 10.

In plain words
What is it for?
Use it to define security requirements, model threats, validate inputs, add CI/CD security checks, review releases, and manage risks from third-party software.
Why use it?
It helps teams consider security throughout development instead of waiting until a release review to look for problems.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is Hack23/European-Parliament-MCP-Server's own configuration. It tells Claude Code and Codex how to work on European-Parliament-MCP-Server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything European-Parliament-MCP-Server configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Hack23/European-Parliament-MCP-Server/main/.github/skills/secure-development-lifecycle/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Hack23/European-Parliament-MCP-Server

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for secure-development-lifecycle

README.md
[![agentmods](https://agentmods.dev/badge/skills/hack23/european-parliament-mcp-server/secure-development-lifecycle/github.svg)](https://agentmods.dev/skills/hack23/european-parliament-mcp-server/secure-development-lifecycle)
Your own site
<a href="https://agentmods.dev/skills/hack23/european-parliament-mcp-server/secure-development-lifecycle"><img src="https://agentmods.dev/badge/skills/hack23/european-parliament-mcp-server/secure-development-lifecycle/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.

agentmods 80×15 button for secure-development-lifecycle

Your own site · 80×15
<a href="https://agentmods.dev/skills/hack23/european-parliament-mcp-server/secure-development-lifecycle"><img src="https://agentmods.dev/badge/skills/hack23/european-parliament-mcp-server/secure-development-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 945 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00945
Opus 5 $0.00016 $0.00473
Sonnet 5 $0.00007 $0.00189
Haiku 4.5 $0.00003 $0.00094

Measured 9d ago against content hash 10c1b05b2622, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

secure-development-lifecycle 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 9d 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.

.github/skills/secure-development-lifecycle/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Secure Development Lifecycle Skill

Purpose

Implement secure development practices across all SDLC phases for TypeScript/Node.js MCP server development, from requirements through deployment.

When to Use

  • ✅ Planning new features with security requirements
  • ✅ Implementing security controls in code
  • ✅ Configuring CI/CD security gates
  • ✅ Conducting security reviews before release
  • ✅ Managing supply chain security

SDLC Security Phases

1. Requirements

  • Define security requirements alongside functional requirements
  • Identify data classification (European Parliament public data, GDPR considerations)
  • Determine compliance requirements (ISMS, GDPR)

2. Design

  • Threat modeling using STRIDE methodology
  • Security architecture documentation (SECURITY_ARCHITECTURE.md)
  • Input validation strategy (Zod schemas)
  • Rate limiting and API security design

3. Implementation

// Security controls in code
import { z } from 'zod';

// Input validation
const schema = z.object({
  id: z.number().int().positive(),
  query: z.string().min(1).max(500),
});

// Error handling (no information leakage)
try {
  const result = await apiCall();
} catch (error) {
  logger.error('API call failed', { error });
  throw new Error('Request failed');  // Generic message
}

4. Testing

  • Unit tests with 80%+ coverage
  • Security-focused tests (input validation, error handling)
  • Dependency scanning (npm audit)
  • License compliance (test:licenses)

5. Deployment

  • Automated security checks in CI/CD
  • CodeQL analysis on every PR
  • SBOM generation for supply chain transparency
  • Signed releases with provenance attestation

6. Monitoring

  • Dependabot alerts for dependency vulnerabilities
  • GitHub secret scanning
  • Regular security audits

Supply Chain Security

Control Implementation
OSSF Scorecard Automated scoring of security practices
SLSA Level Build provenance and supply chain integrity
SBOM CycloneDX software bill of materials
Dependency pinning package-lock.json committed
Signed commits GPG-signed git commits

Read the full file on GitHub · 104 lines

Changes

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.

  1. 9d ago First seen · 104 lines · 33 tokens per session scan A 10c1b05b2622

Subscribe to this mod's changes

secure-development-lifecycle is a skill published in the GitHub repository Hack23/European-Parliament-MCP-Server (28 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 945 once invoked, about $0.0002 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-30.

Related

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…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

specflow-use

To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.

griddynamics/rosetta · 27 tokens

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.

db-lyon/ue-mcp · 81 tokens

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…

agentfront/frontmcp · 176 tokens

authoring-decorators

Use when the user wants to write a new prompt decorator - either a personal one for their repo or a contribution back to the upstream catalogue. Walks through the JSON schema, the extensions/ convention, how to verify a new decorator end-to-end through the hook, and how to diagnose failures using debug logging and…

synaptiai/prompt-decorators · 72 tokens

apitap

ApiTap gives AI agents cheap access to web data through three layers.

n1byn1kt/apitap · 0 tokens