find-interceptor-impl

A lookup tool for Membrane, which connects XML configuration names in proxies.xml to the Java classes that implement them.

In plain words
What is it for?
Use it to find the Java class behind a tag such as <groovy>, or to find the XML tag associated with a Java class.
Why use it?
It removes the need to search every source folder manually when you know an interceptor or configuration tag but not its implementation class.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/membrane/api-gateway/find-interceptor-impl
Any agent
npx skills add membrane/api-gateway --skill find-interceptor-impl
Clone the repo
git clone --depth 1 https://github.com/membrane/api-gateway

Made for: Claude Code, Codex.

Per session 112 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 587 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00112 $0.00587
Opus 5 $0.00056 $0.00293
Sonnet 5 $0.00022 $0.00117
Haiku 4.5 $0.00011 $0.00059

Measured yesterday against content hash 30febf44547b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

find-interceptor-impl 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.

The scan reads SKILL.md. This mod also ships 1 executable file (find-interceptor-impl.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/find-interceptor-impl/SKILL.md · 55 lines

What it actually says

Find Interceptor Implementation

In Membrane, every interceptor (and most config elements) is wired to an XML config tag by an @MCElement(name = "...") annotation on its Java class. The tag <groovy> in proxies.xml is implemented by the class annotated @MCElement(name = "groovy")GroovyInterceptor. This skill maps between the two directions.

Name → implementation class (the common case)

Run the helper with the XML element name:

.claude/skills/find-interceptor-impl/find-interceptor-impl.sh groovy

It prints the class and file, searching every module's src/main/java (the annotation is not limited to core):

Implementation class for <groovy>:
  GroovyInterceptor  ->  ./core/src/main/java/.../groovy/GroovyInterceptor.java

Class → element name (reverse direction)

Given a class name, find its file and annotation in one shot — no need to know which module it lives in first:

grep -rn --include='GroovyInterceptor.java' '@MCElement' .

The name = "..." value is the tag used in proxies.xml. No match means the class isn't directly configurable — it's likely an abstract base or exposed under a parent element; check its subclasses for the nearest one carrying @MCElement, or grep distribution/examples / proxies.xml for how it's actually used.

Behaviour to trust

  • Several results — some names are declared on more than one class (a base plus an override, or per-module variants); the script lists all of them, pick by package/context.
  • No exact match — exits non-zero and suggests the closest declared names (handles typos like grovygroovy); re-run with the corrected name.
  • Matching is lenient: name need not be the first annotation attribute (@MCElement(component = false, name = "...") is fine), and both name="x" and name = "x" spacings match.
Files

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.

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.

  1. yesterday First seen · 55 lines · 112 tokens per session scan A 30febf44547b

Subscribe to this mod's changes

find-interceptor-impl is a skill published in the GitHub repository membrane/api-gateway (638 stars, last pushed yesterday), licensed Apache-2.0. It adds 112 tokens to every session and 587 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.

Related

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.

organvm-iv-taxis/a-i--skills · 54 tokens

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.

buiphucminhtam/forgewright · 73 tokens

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.

asgarovf/locusai · 37 tokens

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"…

JPeetz/agent-skills · 117 tokens

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-Platform/LAP · 89 tokens

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-Platform/LAP · 89 tokens