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-interceptor-impl/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-interceptor-impl)<a href="https://agentmods.dev/skills/membrane/api-gateway/find-interceptor-impl"><img src="https://agentmods.dev/badge/skills/membrane/api-gateway/find-interceptor-impl/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-interceptor-impl"><img src="https://agentmods.dev/badge/skills/membrane/api-gateway/find-interceptor-impl.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
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 →
- low Excessive Agency · line 23 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00112 | $0.00587 |
| Opus 5.5 | $0.00045 | $0.00235 |
| Sonnet 5.5 | $0.00022 | $0.00117 |
| Haiku 4.5 | $0.00011 | $0.00059 |
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 2mo 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 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
grovy→groovy); re-run with the corrected name. - Matching is lenient:
nameneed not be the first annotation attribute (@MCElement(component = false, name = "...")is fine), and bothname="x"andname = "x"spacings match.
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.
- 2mo ago First seen · 55 lines · 112 tokens per session scan A 30febf44547b
find-interceptor-impl is a skill published in the GitHub repository membrane/api-gateway (656 stars, last pushed yesterday), licensed Apache-2.0. It adds 112 tokens to every session and 587 once invoked, about $0.0004 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.