Menü
Use when adding, removing, enabling/disabling, or reconfiguring a backend in the router's servers.yaml registry (URLs, namespaces, entrypoints, server_name/transform overrides).
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use when `make ci-local` fails locally or a GitHub Actions run reports a CI failure (format, lint, line-budget, typecheck, or test errors).
Use when reviewing a diff, PR, or change set for correctness and quality before merge or handoff. For a deep security-only pass, use security-review instead.
Use when bringing this repo into compliance with a GeneFoundry fleet standard (tool-naming, response-envelope, container-hardening, versioning, MCP transport, or logging) or closing its tracking issue.
Use when preparing to tag, publish, or deploy a genefoundry-router build.
Use when reviewing genefoundry-router security before deploy, when touching auth/proxy/logging/limits config, or when answering an infosec/DSB question.
Use when changing the router's authentication or authorization — JWT/OAuth modes, verifiers, resource/audience metadata, the secure-by-default bind guard, or the no-token-passthrough boundary.
| name | backend-registry-change |
| description | Use when adding, removing, enabling/disabling, or reconfiguring a backend in the router's servers.yaml registry (URLs, namespaces, entrypoints, server_name/transform overrides). |
Follow AGENTS.md first. servers.yaml is the source of truth for the federated fleet; URLs/secrets live in .env.
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.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.make ci-local.url instead of url_env, or forgetting to add the var to .env.transform to patch a naming issue the backend should fix upstream.fleet-probe — a 307 redirect or 0-tool backend passes CI but is dead in prod.