metadome-link: Instructions file for Codex

AGENTS.md

metadome-link AGENTS.md is an instructions file for Codex, OpenCode from berntpopp/metadome-link. It costs 2,697 tokens per session, scanned A, original, MIT.

Repository instructions for working on metadome-link, a read-only server that provides data from the MetaDome human-protein service through MCP and REST interfaces. MCP is a standard way for AI tools to access services.

In plain words
What is it for?
Use it when developing, reviewing, or documenting metadome-link, especially its protein-variant data service, asynchronous behavior, and separation between its data and service interfaces.
Why use it?
It gives contributors the project’s boundaries, data details, and rules in one place, reducing misunderstandings when changing the code or documentation.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is berntpopp/metadome-link's own configuration. It tells Codex and OpenCode how to work on metadome-link itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything metadome-link configures →

Reuse

Borrowing it

Nothing to install: this file belongs to berntpopp/metadome-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.

Copy the file
curl -O https://raw.githubusercontent.com/berntpopp/metadome-link/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/berntpopp/metadome-link

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for metadome-link AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/berntpopp/metadome-link/agents-md/github.svg)](https://agentmods.dev/instructions/berntpopp/metadome-link/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/berntpopp/metadome-link/agents-md"><img src="https://agentmods.dev/badge/instructions/berntpopp/metadome-link/agents-md/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.

agentmods 80×15 button for metadome-link AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/berntpopp/metadome-link/agents-md"><img src="https://agentmods.dev/badge/instructions/berntpopp/metadome-link/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,697 This file is loaded in full into every session.
When invoked 2,697 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02697 $0.02697
Opus 5.5 $0.01079 $0.01079
Sonnet 5.5 $0.00539 $0.00539
Haiku 4.5 $0.00270 $0.00270

Measured 6d ago against content hash 719e2aad74ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

metadome-link AGENTS.md 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 6d 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.

AGENTS.md · 190 lines

How it starts

The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Guidance for agents and contributors working in this repository.

README.md is the front door and follows the GeneFoundry README Standard v1 (hard ceiling 200 lines, fixed section order, machine-checked by scripts/check_readme.py). Depth lives in docs/ — see the documentation index at the bottom of this file. Do not grow the README: relocate.

What this is

metadome-link is a data-reading MCP + REST server with an idempotent build trigger that wraps the MetaDome web service (Wiel et al., Human Mutation 2019). It exposes, per human protein transcript: the per-residue missense tolerance landscape (sw_dn_ds, lower = more intolerant), Pfam domain annotations, meta-domain (homolog) variant aggregation, and per-residue ClinVar annotations. MetaDome does not expose true per-residue gnomAD counts; its explicitly-labelled Pfam aggregates may span genes (GRCh37/hg19 or GRCh38.p14, defaulting to GRCh38.p14). It is one backend in the GeneFoundry -link fleet, federated behind genefoundry-router under the namespace metadome. It mirrors the sibling fleet stack lifted from mondo-link (MCP plane) and mavedb-link (async API client + TTL cache).

Two planes (non-negotiable boundary)

  • Data plane — config.py, constants.py, identifiers.py, exceptions.py, api/, cache/, services/. Talks to MetaDome over async httpx, normalizes the responses, and returns plain dicts. It raises typed exceptions from metadome_link.exceptions; it never builds error envelopes. Unlike most fleet siblings there is no ingest/ step and no local SQLite index of all data — MetaDome has no bulk dump, so this is a live-API proxy + persistent result cache (gtex/mavedb pattern). Completed landscapes are cached on disk (SQLite, keyed (transcript_id, metadome_data_version)); transcript lists use an in-memory TTL cache; /status is never cached.
  • MCP plane — mcp/. Domain-agnostic scaffolding shared with siblings (lifted from mondo-link). run_mcp_tool (in mcp/envelope.py) owns success / _meta and converts exceptions into returned structured errors (never raised to the client).

Read the full file on GitHub · 190 lines

Changes

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.

  1. 6d ago Changed 719e2aad74ad
  2. 1mo ago Changed · +31 lines · +514 tokens per session 121e206cc90c
  3. 1mo ago First seen · 159 lines · 2,183 tokens per session scan A 57c3b4b698bc

Subscribe to this mod's changes

metadome-link AGENTS.md is an instructions file published in the GitHub repository berntpopp/metadome-link (0 stars, last pushed 2d ago), licensed MIT. It adds 2,697 tokens to every session, about $0.0108 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-31.

Related

Other instructions, from other repositories