What is backend-registry-change?

A procedure for changing the registry of backends used by a router, where a backend is a service that provides tools.

Use it to add, remove, enable, disable, or reconfigure a registered backend and refresh the tool discovery catalogue.

It keeps backend URLs, names, namespaces, entry points, and enabled status consistent, then checks that the fleet remains reachable and exposes tools correctly.

How berntpopp/genefoundry-router configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to berntpopp/genefoundry-router. 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/genefoundry-router/main/.claude/skills/backend-registry-change/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/berntpopp/genefoundry-router

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/berntpopp/genefoundry-router/backend-registry-change/github.svg)](https://agentmods.dev/skills/berntpopp/genefoundry-router/backend-registry-change)

Your own site

<a href="https://agentmods.dev/skills/berntpopp/genefoundry-router/backend-registry-change"><img src="https://agentmods.dev/badge/skills/berntpopp/genefoundry-router/backend-registry-change/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/berntpopp/genefoundry-router/backend-registry-change"><img src="https://agentmods.dev/badge/skills/berntpopp/genefoundry-router/backend-registry-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 435 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00042	$0.00435
Opus 5	$0.00021	$0.00217
Sonnet 5	$0.00008	$0.00087
Haiku 4.5	$0.00004	$0.00044

Measured 11d ago against content hash 51133b4447e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

backend-registry-change 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.

.claude/skills/backend-registry-change/SKILL.md · 24 lines

What it actually says

Backend Registry Change

Follow AGENTS.md first. servers.yaml is the source of truth for the federated fleet; URLs/secrets live in .env.

Workflow

Edit the backend's entry in servers.yaml. Keys per server: name, repo, url_env (the .env var holding the URL), namespace, tags, entrypoints; enabled defaults true via the defaults block. Add the URL var to .env / .env.example.
entrypoints seed the discovery catalog / golden tasks — set the common first-call tools for a new backend.
Prefer namespacing over transforms. The current fleet has no transform blocks (all backends adopted Tool-Naming v1). Use server_name only to reconcile a backend whose ratified serverInfo.name differs from its registry alias (e.g. spliceai → spliceailookup-link). If you must add a transform, delete it once the backend fixes naming upstream.
make validate (config schema) → make list-tools (namespaced, collision-free surface) → make fleet-probe (live reachability + non-zero tool harvest; fail loud on 0-tool backends).
make snapshot-catalog to regenerate the discovery catalog; keep the guard test green.
Never expose a backend directly — it stays behind the router / proxy. Run make ci-local.

Common mistakes

Using url instead of url_env, or forgetting to add the var to .env.
Adding a transform to patch a naming issue the backend should fix upstream.
Enabling a backend without fleet-probe — a 307 redirect or 0-tool backend passes CI but is dead in prod.

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.

11d ago First seen · 24 lines · 42 tokens per session scan A 51133b4447e2

Subscribe to this mod's changes

backend-registry-change is a skill published in the GitHub repository berntpopp/genefoundry-router (5 stars, last pushed 5d ago), licensed MIT. It adds 42 tokens to every session and 435 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-31.

Backend and APIs api-gateway bioinformatics claude clinical-genetics fastmcp gateway

adaptyv

How to use the Adaptyv Bio Foundry API and Python SDK for protein experiment design, submission, and results retrieval. Use this skill whenever the user mentions Adaptyv, Foundry API, protein binding assays, protein screening experiments, BLI/SPR assays, thermostability assays, or wants to submit protein sequences for…

K-Dense-AI/scientific-agent-skills · 113 tokens

benchling-integration

Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.

K-Dense-AI/scientific-agent-skills · 50 tokens

implementing-api-abuse-detection-with-rate-limiting

Implement API abuse detection using token bucket, sliding window, and adaptive rate limiting algorithms to prevent DDoS, brute force, and credential stuffing attacks.

xalgorix/xalgorix · 43 tokens

implementing-api-gateway-security-controls

Implements security controls at the API gateway layer including authentication enforcement, rate limiting, request validation, IP allowlisting, TLS termination, and threat protection. The engineer configures API gateways (Kong, AWS API Gateway, Azure APIM, Apigee) to act as a centralized security enforcement point…

xalgorix/xalgorix · 106 tokens

implementing-api-schema-validation-security

Implement API schema validation using OpenAPI specifications and JSON Schema to enforce input/output contracts and prevent injection, data exposure, and mass assignment attacks.

xalgorix/xalgorix · 35 tokens

securing-api-gateway-with-aws-waf

Securing API Gateway endpoints with AWS WAF by configuring managed rule groups for OWASP Top 10 protection, creating custom rate limiting rules, implementing bot control, setting up IP reputation filtering, and monitoring WAF metrics for security effectiveness.

xalgorix/xalgorix · 59 tokens

genefoundry-router: Skill for Claude Code