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/find-examplenpx skills add membrane/api-gateway --skill find-examplegit clone --depth 1 https://github.com/membrane/api-gatewayWhat 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.00113 | $0.00616 |
| Opus 5 | $0.00056 | $0.00308 |
| Sonnet 5 | $0.00023 | $0.00123 |
| Haiku 4.5 | $0.00011 | $0.00062 |
Grade A, and why
find-example 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Examples and Tutorials
Membrane ships runnable demos in two trees:
distribution/examples/<category>/<name>/— a self-contained example, usually with aproxies.xmland/orapis.yamlconfig plus aREADME.md.distribution/tutorials/<category>/NN-Title.yaml— numbered, self-teaching tutorial steps (one YAML file each).
An element appears in these as a config tag — <call .../> in XML or - call:
in YAML. This skill greps both trees for that tag and reports where the element
is actually used (not just mentioned in prose). It's the inverse of
find-interceptor-impl: that maps a name to its Java class, this maps a name to
its demos.
Usage
Run the helper with the element name (the @MCElement(name = "...") value):
.claude/skills/find-example/find-example.sh call
It lists example directories (with the first line of each README as a summary) and tutorial files:
Examples using <call>:
distribution/examples/orchestration/call-get To provide simpler interfaces ...
distribution/examples/orchestration/call-post To automate backend interactions ...
Tutorials using <call>:
distribution/tutorials/orchestration/20-For-Loop-Call.yaml
distribution/tutorials/orchestration/40-Authentication-Call.yaml
Narrow to one tree when that's all the user wants:
.claude/skills/find-example/find-example.sh rewriter --tutorials
.claude/skills/find-example/find-example.sh apiKey --examples
Behaviour to trust
- Matches config, not prose. Only
proxies.xml,*.yamland*.ymlare searched, against both the XML (<name ...>) and YAML (name:) tag forms, so a README that merely names the element won't produce a false hit. - Examples are deduped to their directory; tutorials are listed per file
(they're individual steps sharing one category directory).
- No match → exit 3. Either the element genuinely has no demo, or the name is
off. Confirm the name with
find-interceptor-impland retry.
- No match → exit 3. Either the element genuinely has no demo, or the name is
off. Confirm the name with
What ships with it
1 file 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.
- yesterday First seen · 58 lines · 113 tokens per session scan A b7eb8bbf4a78
find-example is a skill published in the GitHub repository membrane/api-gateway (638 stars, last pushed yesterday), licensed Apache-2.0. It adds 113 tokens to every session and 616 once invoked, about $0.0006 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-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"…
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…
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…