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/contribution-guidelines/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/contribution-guidelines)<a href="https://agentmods.dev/skills/hack23/european-parliament-mcp-server/contribution-guidelines"><img src="https://agentmods.dev/badge/skills/hack23/european-parliament-mcp-server/contribution-guidelines/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/contribution-guidelines"><img src="https://agentmods.dev/badge/skills/hack23/european-parliament-mcp-server/contribution-guidelines.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 MCP Rug Pull · line 67 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00023 | $0.00837 |
| Opus 5.5 | $0.00009 | $0.00335 |
| Sonnet 5.5 | $0.00005 | $0.00167 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
contribution-guidelines 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contribution Guidelines Skill
Purpose
Follow proper open source contribution process including PR workflow, code review standards, and commit conventions.
When to Use
- ✅ Submitting pull requests
- ✅ Conducting code reviews
- ✅ Contributing to open source
- ✅ Reporting bugs or requesting features
Pull Request Process
1. Fork and Clone
git clone https://github.com/YOUR-USERNAME/European-Parliament-MCP-Server.git
cd European-Parliament-MCP-Server
git remote add upstream https://github.com/Hack23/European-Parliament-MCP-Server.git
2. Create Feature Branch
git checkout -b feature/new-mcp-tool
3. Make Changes
npm ci # Install dependencies
npm run lint # Check code style
npm test # Run tests
npm run build # Verify build
4. Commit with Conventional Commits
git commit -m "feat: add search_votes MCP tool"
git commit -m "fix: handle API timeout in MEP lookup"
git commit -m "docs: update SECURITY_ARCHITECTURE.md"
git commit -m "test: add integration tests for committee API"
5. Submit PR
git push origin feature/new-mcp-tool
# Create PR via GitHub UI
Code Review Checklist
For Contributors
- ✅ All tests pass (
npm test) - ✅ Lint passes (
npm run lint) - ✅ TypeScript type check passes (
npx tsc --noEmit) - ✅ Code follows project conventions
- ✅ Documentation updated
- ✅ No secrets committed
- ✅ Test coverage maintained (80%+)
For Reviewers
- ✅ Code is maintainable and well-typed
- ✅ Input validation with Zod schemas
- ✅ Error handling follows patterns
- ✅ Security implications considered
- ✅ ISMS policy compliance verified
- ✅ Performance impact acceptable
Commit Types
| Type | Description |
|---|---|
| feat | New functionality |
| fix | Bug fix |
| docs | Documentation only |
| style | Code style (formatting) |
| refactor | Code restructuring |
| test | Adding/updating tests |
| chore | Maintenance tasks |
| security | Security fix |
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 · 110 lines · 23 tokens per session scan A 9cbc5c40f953
contribution-guidelines is a skill published in the GitHub repository Hack23/European-Parliament-MCP-Server (29 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 837 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
git-workflow
Branching and review conventions.
zen-comprehensive-review
Orchestrate a multi-model code review: spawn 3 review subagents, merge findings. In PR mode, posts GitHub PR comments with reactions. In local mode, outputs findings directly. CRITICAL: this skill is costly, don't use it unless user explicitly requested to use it.
git-workflow
Follow this team's Git conventions for branching, commit messages, and pull requests.
gitlab-merge-request-review
Review and merge GitLab merge requests via the gitlab-api MCP server — by default the MRs assigned to you or where you are a reviewer, optionally scoped to a project, group, or the whole instance. Read an MR, gate it on a green pipeline (pipeline → jobs → job log), then approve, accept/merge, or set…
repository-manager-candidate-certification
Understand and verify a branch candidate's and a sealed generation's certification state — the Candidate/Generation lifecycle vocabulary, the validation-stage/evidence model, and the rmconceptsverifycandidate / verifygeneration marker-collision checks — before trusting a merge-queue outcome as landable. This is the…
pr-analysis
Analyse a GitHub pull request by fetching its metadata, diff, linked issues and CI status.