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/create-tutorial/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/create-tutorial)<a href="https://agentmods.dev/skills/membrane/api-gateway/create-tutorial"><img src="https://agentmods.dev/badge/skills/membrane/api-gateway/create-tutorial/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/create-tutorial"><img src="https://agentmods.dev/badge/skills/membrane/api-gateway/create-tutorial.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00097 | $0.02809 |
| Opus 5.5 | $0.00039 | $0.01124 |
| Sonnet 5.5 | $0.00019 | $0.00562 |
| Haiku 4.5 | $0.00010 | $0.00281 |
Grade A, and why
create-tutorial scanned grade A with 1 finding 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 15d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Membrane config (e.g. a curl-only walkthrough against a hosted API). A `.md` step gets no How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a Tutorial
In this repo a tutorial is usually a runnable, self-teaching YAML config. The leading comment block of the file is the lesson; the config below it is the working example the reader runs. A complete tutorial therefore has three parts, and they must stay in sync:
- The numbered YAML in
distribution/tutorials/<category>/— the lesson plus the config. - Category support files —
membrane.sh,membrane.cmd, aREADME.md(andrun-docker.*where the category offers Docker), so the reader can actually start it. - An integration test under
distribution/src/test/java/com/predic8/membrane/tutorials/…so the tutorial can't silently rot. These tests unzip the built distribution and start Membrane against the tutorial's YAML, so a broken example fails CI.
A tutorial step can also be a plain .md file — use this when the step needs no local
Membrane config (e.g. a curl-only walkthrough against a hosted API). A .md step gets no
integration test; it just lives alongside the numbered YAMLs and is linked from the README.
Work through the steps below in order. The reader of a tutorial follows the file top-to-bottom with no other docs open, so the single most important thing is that the YAML teaches itself.
Step 1 — Choose the category and filename
Categories live under distribution/tutorials/: getting-started, json, xml, advanced,
transformation, security, jwt, api-keys, oauth2, soap, soap-rest-converter,
wsdl-to-openapi, orchestration, sse, mcp, llm-gateway. Pick the one that fits; only
create a new category if nothing fits (see "New category" at the end).
Files are numbered NN-Title.yaml (e.g. 10-PathParameters.yaml). The number sets reading
order. List the directory and pick the next gap — convention leaves room between numbers
(10, 20, 30…) so steps can be inserted later. Match the existing PascalCase-with-hyphens
title style.
Step 2 — Write the YAML (the lesson lives here)
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.
- 15d ago Changed · +17 lines a8e6e40dfecc
- 1mo ago Changed · +2 lines 236f826f41cd
- 2mo ago First seen · 215 lines · 97 tokens per session scan A 860c09fc35b4
create-tutorial is a skill published in the GitHub repository membrane/api-gateway (656 stars, last pushed yesterday), licensed Apache-2.0. It adds 97 tokens to every session and 2,809 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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.