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/incident-response/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/incident-response)<a href="https://agentmods.dev/skills/hack23/european-parliament-mcp-server/incident-response"><img src="https://agentmods.dev/badge/skills/hack23/european-parliament-mcp-server/incident-response/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/incident-response"><img src="https://agentmods.dev/badge/skills/hack23/european-parliament-mcp-server/incident-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00804 |
| Opus 5.5 | $0.00011 | $0.00322 |
| Sonnet 5.5 | $0.00006 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
incident-response 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- security-by-design — 88% identical, 979 lines differ
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response Skill
Purpose
Establish procedures for detecting, analyzing, containing, and recovering from security incidents affecting MCP server projects.
When to Use
- ✅ Responding to security vulnerability reports
- ✅ Handling dependency compromise alerts
- ✅ Managing secret exposure incidents
- ✅ Addressing CodeQL critical findings
- ✅ Processing SECURITY.md vulnerability disclosures
Incident Classification
| Severity | Examples | Response Time |
|---|---|---|
| 🔴 Critical | Secret exposure, RCE vulnerability | 4 hours |
| 🟠 High | Authentication bypass, data exposure | 24 hours |
| 🟡 Medium | XSS, CSRF, moderate vulnerability | 72 hours |
| 🟢 Low | Information disclosure, minor issues | 1 week |
Response Workflow
1. Detection & Triage
- GitHub Security Advisories notification
- Dependabot critical alert
- Security researcher disclosure via SECURITY.md
- CodeQL/SAST finding in CI
2. Containment
# If secret exposed
# 1. Rotate immediately
# 2. Revoke old credentials
# 3. Review access logs
# If vulnerable dependency
npm audit fix
# or pin to safe version
npm install package@safe-version
3. Eradication
- Apply security patch
- Update vulnerable dependencies
- Fix code vulnerability
- Verify fix with security tests
4. Recovery
- Deploy fixed version
- Verify no unauthorized access occurred
- Monitor for residual effects
- Update security documentation
5. Lessons Learned
- Document incident timeline
- Update detection mechanisms
- Improve prevention controls
- Share findings with team
Communication
- Use GitHub Security Advisories for coordinated disclosure
- Follow responsible disclosure timeline in SECURITY.md
- Notify affected users if personal data involved (GDPR)
ISMS Policy References
Core policies:
- Incident Response Plan — Primary policy: NIST SP 800-61r2 lifecycle (Prep → Detection → Analysis → Containment → Eradication → Recovery → Lessons Learned)
- Information Security Policy — Governance, transparency, stakeholder communication
- Privacy Policy — GDPR Art. 33/34 breach notification (≤ 72 h to DPA)
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 · 96 lines · 28 tokens per session scan A 850ab9cfc9ae
incident-response 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 804 once invoked, about $0.0001 per session on Opus 5.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.
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.