Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/membrane/api-gateway/membrane-confignpx skills add membrane/api-gateway --skill membrane-configgit clone --depth 1 https://github.com/membrane/api-gatewayWrote 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/membrane/api-gateway/membrane-config)<a href="https://agentmods.dev/skills/membrane/api-gateway/membrane-config"><img src="https://agentmods.dev/badge/skills/membrane/api-gateway/membrane-config.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 | $0.00167 | $0.01514 |
| Opus 5 | $0.00084 | $0.00757 |
| Sonnet 5 | $0.00033 | $0.00303 |
| Haiku 4.5 | $0.00017 | $0.00151 |
Grade A, and why
membrane-config scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
useful, a `curl` line to try it. Add short comments in that spirit — explain How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Membrane configuration generator
Membrane is configured declaratively. The modern format is apis.yaml; a legacy
Spring proxies.xml format also exists. This skill produces correct, idiomatic
config by doing what a careful engineer does: copy the shape from a real working
example, confirm exact attribute names against the schema, and validate before
handing it over.
Two sources of truth, and they play different roles:
distribution/tutorials/**/*.yaml— idiom and style. Heavily commented, curated, and the best examples in the repo. Treat these as gold.distribution/examples/**adds more (includingproxies.xml).membrane.schema.json— what's actually allowed: every element, its exact attribute names, enum values, and nesting. The model's main failure mode is inventing plausible-but-wrong attribute names; the schema is how you avoid that.
Don't generate config from memory alone. The element set is large (~255 elements) and evolves; ground every snippet.
Workflow
-
Clarify intent only if needed. What should the gateway do? Default to one
apion port2000forwarding to atarget.urlunless the request implies otherwise. Don't over-ask — most requests map cleanly onto a known pattern. -
Find a close example. Skim references/cheatsheet.md for the matching pattern, then look at the real tutorial for the live version:
grep -rl "rateLimiter:" distribution/tutorials distribution/examplesReading the closest tutorial is the single highest-leverage step — it carries ordering, nesting, and conventions you'd otherwise guess at.
-
Confirm exact attributes against the schema for every non-trivial element. Guessing attribute names is the main way these configs go wrong:
python3 scripts/describe_element.py rateLimiter # attributes + enums + children python3 scripts/describe_element.py --grep auth # discover element names python3 scripts/describe_element.py --list # all element ids
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 119 lines · 167 tokens per session scan A 62b00ff8e510
membrane-config is a skill published in the GitHub repository membrane/api-gateway (640 stars, last pushed today), licensed Apache-2.0. It adds 167 tokens to every session and 1,514 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
api-design-patterns
Design robust APIs with RESTful patterns, GraphQL schemas, versioning strategies, and error handling conventions. Supports OpenAPI/Swagger documentation and SDK generation patterns. Triggers on API design, schema definition, endpoint architecture, or developer experience requests.
api-designer
Designs production-grade APIs — REST, GraphQL, gRPC, and AsyncAPI patterns including pagination, versioning, error handling, rate limiting, and API governance. Use when the user asks to design APIs, create endpoints, build an API layer, write OpenAPI specs, or needs help with REST/GraphQL/gRPC service design.
api-design
Design and implement RESTful APIs with proper routing, validation, error handling, and documentation. Use when building new API endpoints, designing API architecture, or improving existing APIs.
api-design-first
Design-first API development skill. Generates OpenAPI 3.1 specifications, enforces REST design best practices, validates endpoints, handles versioning, pagination, error formatting, authentication patterns, rate limiting, and idempotency. Activates when users say "design an API", "create OpenAPI spec", "API endpoint"…
construtor-de-api
Construção e documentação de APIs REST e GraphQL: design de endpoints, versionamento, autenticação, tratamento de erros, documentação OpenAPI 3.0 e boas práticas de segurança e performance.
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…