Borrowing it
Nothing to install: this file belongs to membrane/api-gateway. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/membrane/api-gateway/master/.claude/skills/find-example/SKILL.mdgit 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/find-example)<a href="https://agentmods.dev/skills/membrane/api-gateway/find-example"><img src="https://agentmods.dev/badge/skills/membrane/api-gateway/find-example/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.
<a href="https://agentmods.dev/skills/membrane/api-gateway/find-example"><img src="https://agentmods.dev/badge/skills/membrane/api-gateway/find-example.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 45 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00113 | $0.00605 |
| Opus 5.5 | $0.00045 | $0.00242 |
| Sonnet 5.5 | $0.00023 | $0.00121 |
| Haiku 4.5 | $0.00011 | $0.00060 |
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 21d 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.
What it actually says
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 rateLimiter
It lists example directories (with the first line of each README as a summary) and tutorial files:
Examples using <rateLimiter>:
distribution/examples/rate-limiting The `rateLimiter` helps you maintain ...
distribution/examples/xml/namespaces Namespaces are a powerful XML feature ...
Tutorials using <rateLimiter>:
distribution/tutorials/operation/70-Production-Settings.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.
- 21d ago Changed · -1 lines 4be73e11d90e
- 2mo ago First seen · 58 lines · 113 tokens per session scan A b7eb8bbf4a78
find-example is a skill published in the GitHub repository membrane/api-gateway (656 stars, last pushed yesterday), licensed Apache-2.0. It adds 113 tokens to every session and 605 once invoked, about $0.0005 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-30.
Other skills, from other repositories
fastapi-expert
Expert-level FastAPI development for high-performance Python APIs with async support. Use when the user mentions Python, API, async, REST, OpenAPI, or Pydantic, or when the task involves FastAPI Features.
openapi-expert
Expert-level OpenAPI/Swagger specification for API design, documentation, and code generation. Use when the user mentions swagger, API specs, REST, API design, or documentation, or when the task involves OpenAPI Specification, Webhooks, or Polymorphism.
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.
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-design
Design REST API contracts that are consistent, evolvable, and easy to consume.
REST API Endpoint Designer
Designs RESTful API endpoints following OpenAPI spec and industry best practices.