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/threat-modeling-framework/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/threat-modeling-framework)<a href="https://agentmods.dev/skills/hack23/european-parliament-mcp-server/threat-modeling-framework"><img src="https://agentmods.dev/badge/skills/hack23/european-parliament-mcp-server/threat-modeling-framework/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/threat-modeling-framework"><img src="https://agentmods.dev/badge/skills/hack23/european-parliament-mcp-server/threat-modeling-framework.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 117 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00030 | $0.04046 |
| Opus 5 | $0.00015 | $0.02023 |
| Sonnet 5 | $0.00006 | $0.00809 |
| Haiku 4.5 | $0.00003 | $0.00405 |
Grade A, and why
threat-modeling-framework 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 11d 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 — 429 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Threat Modeling Framework Skill
Context
This skill applies when:
- Designing new features or system components
- Conducting security architecture reviews
- Documenting threat models for SDLC phases
- Identifying security threats using STRIDE methodology
- Creating threat model evidence portfolios
- Integrating threat modeling into CI/CD pipelines
- Reviewing threat models during PR process
This skill enforces Hack23 Secure Development Policy Section 🕷️ requirements for systematic threat analysis.
Rules
1. STRIDE Threat Modeling (Policy Section 🕷️.1)
- Spoofing: Identify authentication and identity verification threats
- Tampering: Identify data integrity and unauthorized modification threats
- Repudiation: Identify logging, audit trail, and non-repudiation threats
- Information Disclosure: Identify confidentiality and data exposure threats
- Denial of Service: Identify availability and resource exhaustion threats
- Elevation of Privilege: Identify authorization and privilege escalation threats
2. Threat Model Documentation (Policy Section 🕷️.1.2)
- System Diagram: Data flow diagrams with trust boundaries
- Asset Identification: Critical assets and their classification
- Threat Enumeration: STRIDE threats for each component
- Mitigation Strategies: Security controls for each identified threat
- Risk Assessment: Likelihood and impact ratings
- Evidence Links: References to implemented controls in code
3. SDLC Integration (Policy Section 🕷️.1.3)
- Planning Phase: Threat model before design finalization
- Development Phase: Update threat model as design evolves
- Testing Phase: Verify mitigations are implemented
- Release Phase: Threat model sign-off required
- Maintenance Phase: Update threat model for changes
4. Evidence Portfolio (Policy Section 🕷️.2)
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.
- 11d ago First seen · 429 lines · 30 tokens per session scan A 84e6e3a4d52f
threat-modeling-framework is a skill published in the GitHub repository Hack23/European-Parliament-MCP-Server (28 stars, last pushed yesterday), licensed Apache-2.0. It adds 30 tokens to every session and 4,046 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.
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…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
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.
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…
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…
apitap
ApiTap gives AI agents cheap access to web data through three layers.