api-reference

api-reference is a skill for Claude Code, Codex from LuuOW/meridian-mcp. It costs 38 tokens per session (2,762 once invoked), scanned A, original, MIT.

A guide for documenting REST and WebSocket APIs with machine-readable specifications such as OpenAPI and AsyncAPI. It also covers hosted reference pages, examples, error descriptions, and SDK documentation.

In plain words
What is it for?
Use it to write and validate API specifications, document requests and responses, publish reference documentation, and generate SDK references.
Why use it?
It helps keep API documentation structured and useful instead of leaving endpoint behavior scattered across notes or code.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: $skill-name invocation.

Good fit Use it to write and validate API specifications, document requests and responses, publish reference documentation, and generate SDK references.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/luuow/meridian-mcp/api-reference
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.

Any agent
npx skills add LuuOW/meridian-mcp --skill api-reference
Clone the repo
git clone --depth 1 https://github.com/LuuOW/meridian-mcp

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for api-reference

README.md
[![agentmods](https://agentmods.dev/badge/skills/luuow/meridian-mcp/api-reference/github.svg)](https://agentmods.dev/skills/luuow/meridian-mcp/api-reference)
Your own site
<a href="https://agentmods.dev/skills/luuow/meridian-mcp/api-reference"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/api-reference/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.

agentmods 80×15 button for api-reference

Your own site · 80×15
<a href="https://agentmods.dev/skills/luuow/meridian-mcp/api-reference"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/api-reference.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,762 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00038 $0.02762
Opus 5.5 $0.00015 $0.01105
Sonnet 5.5 $0.00008 $0.00552
Haiku 4.5 $0.00004 $0.00276

Measured 1mo ago against content hash fb89f374049f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

api-reference 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 1mo 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.

skills/api-reference/SKILL.md · 402 lines

How it starts

The opening of the file, as written. The whole thing — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.

api-reference

Production patterns for writing, validating, and publishing machine-readable API reference documentation. Covers OpenAPI 3.1, AsyncAPI 2.x, doc generation from code annotations, and consumer-facing reference portals.

OpenAPI 3.1 Document Skeleton

Start from a valid skeleton; fill in the gaps rather than building from scratch.

# openapi.yaml
openapi: "3.1.0"

info:
  title: Acme API
  version: "2.4.0"
  description: |
    REST API for the Acme platform.
    
    **Base URL:** `https://api.acme.io/v2`  
    **Auth:** Bearer token via `Authorization` header  
    **Rate limits:** 1000 req/min per token  
  contact:
    name: Platform Team
    email: [email protected]
    url: https://status.acme.io
  license:
    name: Apache 2.0
    url: https://www.apache.org/licenses/LICENSE-2.0

servers:
  - url: https://api.acme.io/v2
    description: Production
  - url: https://sandbox.acme.io/v2
    description: Sandbox (no billing, safe to test)

tags:
  - name: widgets
    description: Create and manage widgets
  - name: auth
    description: Authentication and token management

paths:
  /widgets:
    get:
      operationId: listWidgets
      tags: [widgets]
      summary: List all widgets
      description: |
        Returns a paginated list of widgets owned by the authenticated account.
        Results are sorted by `created_at` descending.
      parameters:
        - $ref: "#/components/parameters/PageParam"
        - $ref: "#/components/parameters/LimitParam"
        - name: status
          in: query
          schema:
            type: string
            enum: [active, archived, draft]
          description: Filter by widget status
      responses:
        "200":
          description: Paginated list of widgets
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/WidgetList"
              examples:
                default:
                  $ref: "#/components/examples/WidgetListExample"
        "401":
          $ref: "#/components/responses/Unauthorized"
        "429":
          $ref: "#/components/responses/RateLimited"

components:
  parameters:
    PageParam:
      name: page
      in: query
      schema:
        type: integer
        minimum: 1
        default: 1
    LimitParam:
      name: limit
      in: query
      schema:
        type: integer
        minimum: 1
        maximum: 100
        default: 20

  responses:
    Unauthorized:
      description: Missing or invalid authentication token
      content:
        application/json:
          schema:
            $ref: "#/components/schemas/Error"
          example:
            code: UNAUTHORIZED
            message: "Bearer token is missing or expired"
    RateLimited:
      description: Rate limit exceeded
      headers:
        Retry-After:
          schema:
            type: integer
          description: Seconds until the rate limit resets
      content:
        application/json:
          schema:
            $ref: "#/components/schemas/Error"

  schemas:
    Error:
      type: object
      required: [code, message]
      properties:
        code:
          type: string
          description: Machine-readable error code
          example: VALIDATION_ERROR
        message:
          type: string
          description: Human-readable error description
        details:
          type: array
          items:
            type: object
            properties:
              field:
                type: string
              issue:
                type: string

  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

security:
  - BearerAuth: []

Read the full file on GitHub · 402 lines

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. 1mo ago First seen · 402 lines · 38 tokens per session scan A fb89f374049f

Subscribe to this mod's changes

api-reference is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed 7d ago), licensed MIT. It adds 38 tokens to every session and 2,762 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

api-docs-generator

Generate API documentation from code - produce OpenAPI/Swagger specs, Markdown API references, request/response examples, and interactive documentation from source code analysis.

chainlesschain/chainlesschain · 34 tokens

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.

personamanagmentlayer/pcl · 57 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-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

api-design-principles

Master REST API design principles to build intuitive, scalable, and maintainable APIs. Use when designing new APIs, reviewing API specifications, or establishing API design standards.

thapaliyabikendra/ai-artifacts · 38 tokens

scalar-design-system

Scalar's design system — design tokens, theming (@scalar/themes), CSS variables, and the @scalar/components library. Use when designing or implementing Scalar UI, especially with Paper (code-to-design / design-to-code), so output matches real Scalar tokens, colors, typography, spacing, and components instead of…

scalar/scalar · 68 tokens