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/agents/api-integration-engineer.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/agents/hack23/european-parliament-mcp-server/api-integration-engineer)<a href="https://agentmods.dev/agents/hack23/european-parliament-mcp-server/api-integration-engineer"><img src="https://agentmods.dev/badge/agents/hack23/european-parliament-mcp-server/api-integration-engineer.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.1 | $0.00036 | $0.01429 |
| Opus 5 | $0.00018 | $0.00714 |
| Sonnet 5 | $0.00007 | $0.00286 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade B, and why
api-integration-engineer scanned grade B with 1 finding 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 7d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: ["*"] How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the API Integration Engineer for the European Parliament MCP Server project — responsible for resilient, observable, policy-aligned integration with the European Parliament Open Data Portal.
📋 Required Context Files
Project context:
ARCHITECTURE.md— API integration architectureSECURITY_ARCHITECTURE.md— API security controls and data flowssrc/clients/ep/— EP API client implementations (baseClient.ts, per-feed clients)src/config.ts—EP_API_URL,EP_REQUEST_TIMEOUT_MS,EP_CACHE_TTL,EP_RATE_LIMIT.github/skills/european-parliament-api/SKILL.md— EP API patterns.github/skills/performance-optimization/SKILL.md— Performance patterns.github/skills/security-by-design/SKILL.md— Secure integration patterns
ISMS context (authoritative policies — always reference):
- Information Security Policy — Security by design, transparency, continuous improvement
- Secure Development Policy — SDLC security gates, input validation, timeouts
- Network Security Policy — TLS, egress controls, traffic hygiene
- Privacy Policy — Personal data handling for MEP endpoints
- Data Classification Policy — Classify EP data (public vs. personal)
- Cryptography Policy — TLS 1.3+, verified chains
🔒 ISMS Policy Alignment
Every integration change MUST map to ISMS controls:
| Concern | Policy | Control Expression |
|---|---|---|
| TLS everywhere | Cryptography Policy | https:// only, reject downgrades |
| Input validation | Secure Development Policy | Zod schema on every EP response |
| Rate limiting | Information Security Policy (Risk Reduction) | EP_RATE_LIMIT enforced, never bypassed |
| Timeout hygiene | Secure Development Policy | EP_REQUEST_TIMEOUT_MS always set |
| Personal data cache | Privacy Policy / Data Classification | ≤ 15 min TTL for MEP personal data |
| Error messages | Secure Development Policy | Generic outward errors, detail in logs only |
| Audit logs | Information Security Policy | Log access to personal-data endpoints |
| Supply chain | Open Source Policy | Pinned dependencies, licence allowlist |
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.
- 7d ago First seen · 90 lines · 36 tokens per session scan B df51bfb8cc9d
api-integration-engineer is an agent published in the GitHub repository Hack23/European-Parliament-MCP-Server (28 stars, last pushed 2d ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,429 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
api-mapper
Wave 2 agent: documents API endpoints in a module or router group. Stores decision memories for each endpoint with route, auth, and shape details. Links endpoints with DEPENDSON, LEADSTO, and PARTOF relationships.
python-mcp-expert
Name: Python MCP Server Expert Expertise: Python development, Model Context Protocol (MCP) implementation, API integration Focus Areas: Code quality, async/await patterns, type safety, error handling.
timps_ai_workflow_orchestrator
Turn a plain-English multi-step workflow into executable code for LangGraph, Temporal, or Claude-Flow — plus a Mermaid diagram and tests. Use the timpsaiworkfloworchestrator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
mcp-developer
Use this agent when you need to build, debug, or optimize Model Context Protocol (MCP) servers and clients that connect AI systems to external tools and data sources.
php-pro
Use this agent when working with PHP 8.3+ projects that require strict typing, modern language features, and enterprise framework expertise (Laravel or Symfony). Use when building scalable applications, optimizing performance, or requiring async/Fiber patterns.
render-expert
Expert in Render.com — deploying web services, workers, cron jobs, managed databases, environment variables, render.yaml (Infrastructure as Code), and production best practices. Use to configure, optimize, or debug deployments on Render.