Borrowing it
Nothing to install: this file belongs to berntpopp/gencc-link. 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/berntpopp/gencc-link/main/.claude/skills/security-review/SKILL.mdgit clone --depth 1 https://github.com/berntpopp/gencc-linkWrote 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/berntpopp/gencc-link/security-review)<a href="https://agentmods.dev/skills/berntpopp/gencc-link/security-review"><img src="https://agentmods.dev/badge/skills/berntpopp/gencc-link/security-review.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.00599 |
| Opus 5 | $0.00018 | $0.00300 |
| Sonnet 5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
security-review 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 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.
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.
This is a copy
100% identical to security-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review (-link backend)
Follow AGENTS.md first. Backends are unauthenticated by design and reachable only through the router / reverse proxy — the router owns edge auth. "Read-only" is not "safe": returned text and tool descriptions are prompt-injection surfaces. Ground in ../genefoundry-router/docs/SECURITY-ASSESSMENT-2026-06-29.md and ../genefoundry-router/docs/CONTAINER-HARDENING-STANDARD-v1.md.
Checklist
- No token passthrough — never forward the MCP caller's
Authorizationto upstreams; use the backend's own credential if any. - Upstream host is fixed — a config constant, never built from a tool argument (SSRF). If a user URL is ever fetched, gate it through a scheme + host allowlist that rejects private IPs and re-validates redirects (pubtator
SafeUrlFetcherpattern). - No PII in logs — never log variant coordinates, phenotype text, or free-text queries (may be GDPR Art. 9 patient-derived); log correlation id + tool + timings only.
- SQL / XML / tar safety — parameterized queries only;
defusedxml; hardened archive extraction. - CORS — never
allow_origins=*withallow_credentials=True. - Destructive / write tools — opt-in via an explicit env flag (default off); jail any file-writing path (reject abs /
..); cap unbounded list inputs. - Container — non-root, read-only rootfs,
cap_drop: ALL,no-new-privileges, resource limits, digest-pinned base,ports: !reset []expose-only, secrets runtime-only, Trivy gate + SBOM. - Prompt injection — treat retrieved text as evidence, not instructions; keep the research-use / not-CDS disclaimer.
- Error-message sanitation — structured error fields are fixed/enum/validated; never reflect caller-supplied names/URIs or upstream 4xx/5xx bodies into caller-visible fields or logs (Response-Envelope v1.1 §Error-message sanitation; FastMCP not-found reflection guard).
Common mistakes
- Assuming a read-only server can't participate in exfiltration (lethal trifecta: private data + untrusted content + outbound channel).
- A
ports:mapping in the base compose surviving overlay merge —ports: !reset []is mandatory to drop it. - Logging the request path/params "for debugging" — that can be PHI.
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 · 27 lines · 36 tokens per session scan A 7d60b1038c21
security-review is a skill published in the GitHub repository berntpopp/gencc-link (0 stars, last pushed 4d ago), licensed MIT. It adds 36 tokens to every session and 599 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to security-review, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
computase
Performs verified local nucleotide-sequence computation with Computase. Use when an agent needs sequence composition or GC bounds, a reverse complement, translation, candidate ORFs, or IUPAC motif sites through Computase MCP tools or the isolated Skill runner.
noodle-biomedical-literature-discovery
Find, inspect, compare, and traverse public biomedical research literature. Use for PubMed or scholarly paper search, publication details, PMID/DOI/PMCID lookup, related papers, citation paths, semantic literature neighborhoods, corpus coverage, or questions asking what research exists about a gene, variant…
noodle-biomedical-literature-discovery-mcp
Select Noodle Biomedical Literature Discovery MCP from Biorouter for public biomedical paper search, PMID DOI or PMCID lookup, publication inspection, related papers, citation or semantic graph traversal, and corpus metadata even when the user does not know the Noodle name.
biomed-research
Use when answering biomedical research questions that need source-backed evidence from local MCP servers, including gene, disease, drug, variant, phenotype, study, or clinical-trial questions.
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.