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/run-example-testnpx skills add membrane/api-gateway --skill run-example-testgit 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.00050 | $0.01145 |
| Opus 5 | $0.00025 | $0.00573 |
| Sonnet 5 | $0.00010 | $0.00229 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
run-example-test 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Example Test
Runs one example/tutorial integration test from the distribution module in
~2 seconds, bypassing the hardcoded failsafe suite that would otherwise run the
entire example suite (~6 min, some tests need internet).
When to use
- The user wants to run / verify / check a specific example or tutorial test,
e.g.
ChainExampleTest,JwtVerificationExampleTest, a*ExampleTestundercom.predic8.membrane.examples.*, or a*TutorialTestundercom.predic8.membrane.tutorials.*.
The distribution must be built first
The base classes (DistributionExtractingTestcase) unzip
distribution/target/membrane-api-gateway-*.zip and start membrane from the
unzipped distribution — not from the source tree. So the tests only ever see
what was last built. Before running them the distribution must be built at the
repo root with:
mvn clean install -DskipTests
The script does this for you (see below). -DskipTests still compiles tests but
skips running them, which also dodges the German-locale annot test failure on
this machine.
How to run
Invoke the helper script with the test class (simple name, fully-qualified name, or path all work):
.claude/skills/run-example-test/run-example-test.sh ChainExampleTest # fast, ~2s
.claude/skills/run-example-test/run-example-test.sh -b ChainExampleTest # rebuild dist first, then run
With no argument it runs the full example IT suite via failsafe (slow, some tests need internet) — and always rebuilds the distribution first, because the suite runs from the built distribution.
The script:
- Distribution build. For the full suite it always runs
mvn clean install -DskipTestsat the root. For a single test it builds the.ziponly if it is missing, or if you pass-b. - Resolves the class name to its FQN by finding the
.javaunderdistribution/src/test/java. - Incrementally recompiles distribution test classes (offline) so edits to the test class are picked up.
- Runs just that class via a tiny JUnit Platform launcher (
RunOne.java), with the working directory set todistribution/(the tests resolve./target).
What ships with it
2 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.
- 2d ago First seen · 101 lines · 50 tokens per session scan A 616053ceae4d
run-example-test is a skill published in the GitHub repository membrane/api-gateway (638 stars, last pushed 2d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,145 once invoked, about $0.0003 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"…
tests
Write clear, maintainable Vitest and Playwright tests with precise assertions, consistent structure, and strong behavioral coverage.
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…